Unauthenticated package-file disclosure via service-created _link
Published May 19, 2020 · Updated Sep 16, 2024
Improper access control in Open Build Service before 2.10.5 allows remote attackers to read source-disabled package files. The mergeservicerun routine in src/backend/bs_srcserver accepts a service-produced filename targeting _link and copies that output as a package link. A crafted _service file therefore bypasses source-access restrictions and exposes package contents without authentication.
Summary
What happened
Improper access control in Open Build Service before 2.10.5 allows remote attackers to read source-disabled package files. The mergeservicerun routine in src/backend/bs_srcserver accepts a service-produced filename targeting _link and copies that output as a package link. A crafted _service file therefore bypasses source-access restrictions and exposes package contents without authentication.
The record
- CVE
- CVE-2020-8021
- Published
- May 19, 2020
- Updated
- Sep 16, 2024
- Vendor
- OpenSUSE
- Product
- Open Build Service
- Classifications
- CWE-269, T1213
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 19, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=Open Build Service <2.10.5
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