| 1 |
# Security audit of go-tuf |
| 2 |
|
| 3 |
## The Update Framework |
| 4 |
|
| 5 |
## Radoslav Dimitrov - 06/13/2023 |
| 6 |
|
| 7 |
go-tuf, a Go implementation of The Update Framework (TUF), plays a critical role in securely managing |
| 8 |
software updates. Recently, a security assessment conducted by X41 D-Sec GmbH uncovered a few |
| 9 |
security-related findings in go-tuf. The following blog post provides a concise overview of the |
| 10 |
assessment's key findings and recommendations. |
| 11 |
|
| 12 |
The assessment identified two vulnerabilities of medium and low severity in go-tuf, along with |
| 13 |
four additional issues without immediate security implications. Even though there are no |
| 14 |
high-severity issues, these vulnerabilities still pose risks in update integrity and local file |
| 15 |
overwrite scenarios. |
| 16 |
|
| 17 |
To address the vulnerabilities, it was recommended to implement measures such as linking versions |
| 18 |
and making root metadata project-specific. Additionally, validating signatures for all files |
| 19 |
processed by go-tuf will enhance protection against file manipulation during transit. Alongside |
| 20 |
the identified vulnerabilities, the security assessment highlighted that the “keys” directory had |
| 21 |
been assigned with world-readable permissions. Although this does not directly expose key files to |
| 22 |
local attackers, it is considered a best practice to assign only the minimum necessary permissions. |
| 23 |
|
| 24 |
Despite the discovery of only a few vulnerabilities and weaknesses, go-tuf demonstrates a high level |
| 25 |
of maturity in terms of security. The security assessment conducted by X41 D-Sec GmbH underscores |
| 26 |
the importance of continuously improving the project's security posture and implementing best practices. |
| 27 |
Alongside maintaining the project, the maintainers of go-tuf are also working on a new code base |
| 28 |
which is based on the positive redesign of python-tuf. This new code base is designed to be more |
| 29 |
efficient, user-friendly, and easier to maintain. The ongoing efforts of the maintainers to improve |
| 30 |
the project's design and simplicity will contribute to the overall health and long-term success |
| 31 |
of go-tuf. By implementing the recommended measures, adhering to best practices, and leveraging |
| 32 |
the advancements in the new code base, go-tuf will continue to provide a reliable and secure solution |
| 33 |
for managing software updates. |