Open Build Service vulnerabilitiesRanked by how likely they are to be used.
Open Build Service is made by Opensuse. We track 22 published vulnerabilities in it, across 154 versions. None of them is on the list of flaws known to be exploited today. If you run Open Build Service, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Open Build Service vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Open Build Service's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Open Build Service flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 1.9%CVE-2014-0593Critical
The set_version script as shipped with obs-service-set_version is a source validator for the Open Build Service (OBS).
- 1.9%CVE-2022-21949High
A Improper Restriction of XML External Entity Reference vulnerability in SUSE Open Build Service allows remote attackers to reference external entities in certain operations.
- 1.8%CVE-2018-12473High
A path traversal traversal vulnerability in obs-service-tar_scm of Open Build Service allows remote attackers to cause access files not in the current build.
- 1.7%CVE-2018-12479High
A Improper Input Validation vulnerability in Open Build Service allows remote attackers to cause DoS by specifying crafted request IDs.
- 1.6%CVE-2011-4183Critical
A vulnerability in open build service allows remote attackers to upload arbitrary RPM files.
- 1.5%CVE-2018-12478Medium
A Improper Input Validation vulnerability in Open Build Service allows remote attackers to extract files from the system where the service runs.
- 1.4%CVE-2011-4181High
A vulnerability in open build service allows remote attackers to gain access to source files even though source access is disabled.
- 1.3%CVE-2011-3178High
In the web ui of the openbuildservice before 2.3.0 a code injection of the project rebuildtimes statistics could be used by authorized attackers to execute shellcode.
- 1.3%CVE-2020-8021Medium
a Improper Access Control vulnerability in of Open Build Service allows remote attackers to read files of an OBS package where the sourceaccess/access is disabled This issue affects: Open Build Service versions prior...
- 1.2%CVE-2018-7689Medium
Lack of permission checks in the InitializeDevelPackage function in openSUSE Open Build Service before 2.9.3 allowed authenticated users to modify packages where they do not have write permissions.
Running Open Build Service? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
The set_version script as shipped with obs-service-set_version is a source validator for the Open Build Service (OBS). In versions prior to 0.5.3-1.1 this script did not properly sanitize the input provided by the user, allowing for code execution on the executing server.
- Matched to
- Open Build Service on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 22 published vulnerabilities listed under the name Open Build Service, across 154 versions.
None of Open Build Service's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Open Build Service. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.