| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in osc 0.133. This vulnerability affects unknown code of the component Status. Performing a manipulation results in access control. This vulnerability was named CVE-2012-1095. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in osc 0.133. This affects an unknown functionality of the component status. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
osc before 0.134 might allow remote OBS repository servers or package maintainers to execute arbitrary commands via a crafted (1) build log or (2) build status that contains an escape sequence for a terminal emulator.
The weakness was presented 02/06/2014 by Jan Lieskovsky as Bug 798353 as not defined bug report (Bugzilla). The advisory is shared at bugzilla.redhat.com. This vulnerability is uniquely identified as CVE-2012-1095 since 02/14/2012. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 74572 (openSUSE Security Update : osc (openSUSE-SU-2012:0400-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks.
Upgrading to version 0.134 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (74572), SecurityFocus (BID 65658†) and Vulnerability Center (SBV-44790†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 74572
Nessus Name: openSUSE Security Update : osc (openSUSE-SU-2012:0400-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: osc 0.134
Timeline
02/14/2012 🔍02/28/2012 🔍
02/28/2012 🔍
02/06/2014 🔍
02/06/2014 🔍
06/05/2014 🔍
06/13/2014 🔍
03/24/2015 🔍
02/01/2022 🔍
Sources
Advisory: Bug 798353Researcher: Jan Lieskovsky
Status: Not defined
Confirmation: 🔍
CVE: CVE-2012-1095 (🔍)
GCVE (CVE): GCVE-0-2012-1095
GCVE (VulDB): GCVE-100-66333
SecurityFocus: 65658 - openSUSE OSC Escape Sequence in Build Log and Build Status Command Injection Vulnerability
Vulnerability Center: 44790 - osc Before 0.134 Remote Code Execution via Crafted Build Log / Build Status, High
Entry
Created: 03/24/2015 15:54Updated: 02/01/2022 12:46
Changes: 03/24/2015 15:54 (60), 05/30/2017 09:12 (7), 02/01/2022 12:46 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.