Information disclosure and service interruption via link following
Published Nov 28, 2024 · Updated Nov 28, 2024
Link-following flaws in obs-scm-bridge before 0.5.2 allow attackers to disclose data or interrupt service using crafted Git repositories. SUSE identifies improper link resolution before file access but does not publish the affected function, path checks, or exact file operations. Exploitation requires a user or build workflow to process an attacker-created repository locally; the affected operations can also modify data handled by the bridge.
Summary
What happened
Link-following flaws in obs-scm-bridge before 0.5.2 allow attackers to disclose data or interrupt service using crafted Git repositories. SUSE identifies improper link resolution before file access but does not publish the affected function, path checks, or exact file operations. Exploitation requires a user or build workflow to process an attacker-created repository locally; the affected operations can also modify data handled by the bridge.
The record
- CVE
- CVE-2024-22038
- Published
- Nov 28, 2024
- Updated
- Nov 28, 2024
- Vendor
- OpenSUSE
- Product
- openSUSE Factory
- Classifications
- CWE-59
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 28, 2024CVE publishedPublication date reported by the CVE source.
- Nov 28, 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=0 <0.5.2
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