Authenticated code injection via inherited Gerrit approvals
Published Apr 16, 2025 · Updated May 20, 2025
Improper access control in Google ChromeOS 16063.87.0 allows remote authenticated users to inject code through ChromiumOS Gerrit. Gerrit's project.config grants registered users addPatchSet access, while inherited copy conditions preserve prior approvals when a malicious revision is added. A registered Gerrit account can therefore replace an approved patch set before automated submission, enabling malicious code to enter builds and interrupt downstream systems.
Summary
What happened
Improper access control in Google ChromeOS 16063.87.0 allows remote authenticated users to inject code through ChromiumOS Gerrit. Gerrit's project.config grants registered users addPatchSet access, while inherited copy conditions preserve prior approvals when a malicious revision is added. A registered Gerrit account can therefore replace an approved patch set before automated submission, enabling malicious code to enter builds and interrupt downstream systems.
The record
- CVE
- CVE-2025-1568
- Published
- Apr 16, 2025
- Updated
- May 20, 2025
- Vendor
- Product
- ChromeOS
- Classifications
- CWE-284, T1195.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 2025CVE publishedPublication date reported by the CVE source.
- May 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=16063.87.0 <16063.87.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- ChromiumOS code injection proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo