| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Red Hat openshift 1.0/1.0.5. Affected is the function lockwrap. Performing a manipulation results in access control.
This vulnerability is known as CVE-2013-0164. No exploit is available.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in Red Hat openshift 1.0/1.0.5 (Virtualization Software). It has been classified as problematic. This affects the function lockwrap. 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 integrity, and availability. The summary by CVE is:
The lockwrap function in port-proxy/bin/openshift-port-proxy-cfg in Red Hat OpenShift Origin before 1.1 allows local users to overwrite arbitrary files via a symlink attack on a temporary file with a predictable name in /tmp.
The weakness was published 02/24/2013 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2013-0164 since 12/06/2012. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 119431 (RHEL 6 : openshift (RHSA-2013:0220)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Red Hat Local Security Checks and running in the context l.
Upgrading to version 1.0 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (119431) and SecurityFocus (BID 58168†). Similar entries are available at VDB-63643, VDB-63642 and VDB-63641. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.redhat.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.1VulDB Meta Temp Score: 4.9
VulDB Base Score: 5.1
VulDB Temp Score: 4.9
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: Partially
Local: Yes
Remote: No
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: 119431
Nessus Name: RHEL 6 : openshift (RHSA-2013:0220)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: openshift 1.0
Patch: github.com
Timeline
12/06/2012 🔍01/31/2013 🔍
02/24/2013 🔍
02/24/2013 🔍
03/24/2015 🔍
12/06/2018 🔍
12/29/2021 🔍
Sources
Vendor: redhat.comAdvisory: RHSA-2013:0220
Status: Not defined
Confirmation: 🔍
CVE: CVE-2013-0164 (🔍)
GCVE (CVE): GCVE-0-2013-0164
GCVE (VulDB): GCVE-100-63645
SecurityFocus: 58168
See also: 🔍
Entry
Created: 03/24/2015 12:22Updated: 12/29/2021 15:48
Changes: 03/24/2015 12:22 (54), 02/25/2019 10:40 (6), 12/29/2021 15:35 (4), 12/29/2021 15:41 (2), 12/29/2021 15:48 (1)
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.