Cross-site scripting via unescaped feature names
Published Aug 24, 2023 · Updated Sep 30, 2024
Cross-site scripting in Rust Project Cargo 1.60.0 and later, before 1.72, allows attackers to execute JavaScript via timing reports. The cargo build --timings renderer writes dependency feature names into generated HTML without escaping them, so a crafted name becomes executable markup. Exposure requires a git, local-path, or alternative-registry dependency and a user to upload and view the report on a credentialed domain; crates.io-only dependencies are unaffected.
Summary
What happened
Cross-site scripting in Rust Project Cargo 1.60.0 and later, before 1.72, allows attackers to execute JavaScript via timing reports. The cargo build --timings renderer writes dependency feature names into generated HTML without escaping them, so a crafted name becomes executable markup. Exposure requires a git, local-path, or alternative-registry dependency and a user to upload and view the report on a credentialed domain; crates.io-only dependencies are unaffected.
The record
- CVE
- CVE-2023-40030
- Published
- Aug 24, 2023
- Updated
- Sep 30, 2024
- Vendor
- Rust Project
- Product
- Cargo
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2023CVE publishedPublication date reported by the CVE source.
- Sep 30, 2024Record 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=>= 1.60.0, < 1.72
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
- Crafted feature-name timing-report XSS payloadproof 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