Diff misrepresentation via encoded repository paths
Published Aug 8, 2024 · Updated Aug 29, 2024
Improper output encoding in affected GitLab CE/EE releases allows remote authenticated users to misrepresent repository diffs via encoded paths. An encoded repository path reaches the web diff renderer and causes the interface to render the diff incorrectly; GitLab has not publicly disclosed the exact rendering operation. A user with project access must create the encoded path and another user must view the affected diff, allowing the displayed change to differ from repository content.
Summary
What happened
Improper output encoding in affected GitLab CE/EE releases allows remote authenticated users to misrepresent repository diffs via encoded paths. An encoded repository path reaches the web diff renderer and causes the interface to render the diff incorrectly; GitLab has not publicly disclosed the exact rendering operation. A user with project access must create the encoded path and another user must view the affected diff, allowing the displayed change to differ from repository content.
The record
- CVE
- CVE-2024-6329
- Published
- Aug 8, 2024
- Updated
- Aug 29, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-116, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 8, 2024CVE publishedPublication date reported by the CVE source.
- Aug 29, 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=17.1 <17.1.4
- Affected versionversion=17.2 <17.2.2
- Affected versionversion=8.16 <17.0.6
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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