Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revisionBoth sides next revision
advisory:2024-12-06 [2024/12/06 11:00] – adapt commits with fixes ynezzadvisory:2024-12-06 [2024/12/06 12:05] – Add timeline ynezz
Line 3: Line 3:
 ===== DESCRIPTION ===== ===== DESCRIPTION =====
  
-Due to the combination of the command injection in the `openwrt/imagebuilderimage and the truncated SHA-256 hash included in the build request hash, an attacker can pollute the legitimate image by providing a package list that causes the hash collision. The issue consists of two main components:+Due to the combination of the command injection in the openwrt/imagebuilderimage and the truncated SHA-256 hash included in the build request hash, an attacker can pollute the legitimate image by providing a package list that causes the hash collision. The issue consists of two main components:
  
-1. **Command Injection in Imagebuilder**: During image builds, user-supplied package names are incorporated into `makecommands without proper sanitization. This allows malicious users to inject arbitrary commands into the build process, resulting in the production of malicious firmware images signed with the legitimate build key.+1. **Command Injection in Imagebuilder**: During image builds, user-supplied package names are incorporated into 'makecommands without proper sanitization. This allows malicious users to inject arbitrary commands into the build process, resulting in the production of malicious firmware images signed with the legitimate build key.
  
 2. **Truncated SHA-256 Hash Collisions**: The request hashing mechanism truncates SHA-256 hashes to only 12 characters. This significantly reduces entropy, making it feasible for an attacker to generate collisions. By exploiting this, a previously built malicious image can be served in place of a legitimate one, allowing the attacker to "poison" the artifact cache and deliver compromised images to unsuspecting users. 2. **Truncated SHA-256 Hash Collisions**: The request hashing mechanism truncates SHA-256 hashes to only 12 characters. This significantly reduces entropy, making it feasible for an attacker to generate collisions. By exploiting this, a previously built malicious image can be served in place of a legitimate one, allowing the attacker to "poison" the artifact cache and deliver compromised images to unsuspecting users.
Line 31: Line 31:
 ===== CREDITS ===== ===== CREDITS =====
  
-This issue was identified and [[https://github.com/openwrt/asu/security/advisories/GHSA-r3gq-96h6-3v7q|responsibly disclosed]] by security researcher [[https://github.com/Ry0taK|RyotaK]]. +This issue was identified and [[https://github.com/openwrt/asu/security/advisories/GHSA-r3gq-96h6-3v7q|responsibly disclosed]] by security researcher [[https://github.com/Ry0taK|RyotaK]]. 
 + 
 + 
 +===== TIMELINE ===== 
 + 
 + 
 +  * //04.12.2024 2:56 UTC// - Issue reported by @Ry0taK  
 +  * //04.12.2024 ~7:00 UTC// - Official instance on sysupgrade.openwrt.org stopped by @aparcar  
 +  * //04.12.2024 09:42 UTC// - Fix committed and deployed on sysupgrade.openwrt.org by @aparcar  
 +  * //04.12.2024 10:38 UTC// - Investigation if this was actively exploited based on build logs with negative result for the last seven days 
 +  * //04.12.2024 ~11:00 UTC// - Inform known maintainers of ASU instances to upgrade immediately and expect further information soon 
 +  * //05.12.2024 21:57 UTC// - Email to all OpenWrt project members asking for further steps 
 +  * //06.12.2024 ~12:00 UTC// - Release of specific commit showing the issue 
  
 ===== REFERENCES ===== ===== REFERENCES =====
  • Last modified: 2024/12/07 07:31
  • by ynezz