CPE, which stands for Common Platform Enumeration, is a standardized scheme for naming hardware, software, and operating systems. CPE provides a structured naming scheme to uniquely identify and classify information technology systems, platforms, and packages based on certain attributes such as vendor, product name, version, update, edition, and language.
CWE, or Common Weakness Enumeration, is a comprehensive list and categorization of software weaknesses and vulnerabilities. It serves as a common language for describing software security weaknesses in architecture, design, code, or implementation that can lead to vulnerabilities.
CAPEC, which stands for Common Attack Pattern Enumeration and Classification, is a comprehensive, publicly available resource that documents common patterns of attack employed by adversaries in cyber attacks. This knowledge base aims to understand and articulate common vulnerabilities and the methods attackers use to exploit them.
Services & Price
Help & Info
Search : CVE id, CWE id, CAPEC id, vendor or keywords in CVE
Race condition in runner in Install.framework in the Install Framework Legacy component in Apple OS X before 10.10.5 allows attackers to execute arbitrary code in a privileged context via a crafted app that leverages incorrect privilege dropping associated with a locking error.
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Metrics
Metrics
Score
Severity
CVSS Vector
Source
V2
9.3
AV:N/AC:M/Au:N/C:C/I:C/A:C
nvd@nist.gov
EPSS
EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.
EPSS Score
The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.
Date
EPSS V0
EPSS V1
EPSS V2 (> 2022-02-04)
EPSS V3 (> 2025-03-07)
EPSS V4 (> 2025-03-17)
2022-02-06
–
–
2.51%
–
–
2022-04-03
–
–
2.51%
–
–
2022-07-17
–
–
2.51%
–
–
2023-01-08
–
–
3.31%
–
–
2023-03-12
–
–
–
0.27%
–
2023-03-26
–
–
–
0.27%
–
2023-09-10
–
–
–
0.27%
–
2024-02-11
–
–
–
0.27%
–
2024-06-02
–
–
–
0.36%
–
2024-06-09
–
–
–
0.27%
–
2024-09-15
–
–
–
0.38%
–
2024-11-17
–
–
–
0.38%
–
2024-12-22
–
–
–
0.67%
–
2025-01-19
–
–
–
0.67%
–
2025-03-18
–
–
–
–
23.5%
2025-03-18
–
–
–
–
23.5,%
EPSS Percentile
The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
Publication date : 2015-09-09 22h00 +00:00 Author : Google Security Research EDB Verified : Yes
Source: https://code.google.com/p/google-security-research/issues/detail?id=478
The Install.framework runner suid root binary does not correctly account for the fact that Distributed Objects
can be connected to by multiple clients at the same time.
By connecting two proxy objects to an IFInstallRunner and calling [IFInstallRunner makeReceiptDirAt:asRoot:]
in the first and passing a custom object as the directory name we can get a callback to our code just after the
makeReceiptDirAt code has called seteuid(0);setguid(0) to regain privs. Since BSD priviledges are per-process
this means that our other proxy object will now have euid 0 without having to provide an authorization reference.
In this second proxy we can then just call runTaskSecurely and get a root shell before returning from the first proxy's callback function
which will then drop privs.
build using the provided makefile and run passing the full path to the localhost shell
Proof of Concept:
https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/38136.zip