| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Apple iPhone OS up to 1.0.0 and classified as problematic. Affected by this issue is some unknown functionality. Performing a manipulation results in memory corruption. This vulnerability is identified as CVE-2009-2795. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability classified as critical has been found in Apple iPhone OS up to 1.0.0 (Smartphone Operating System). This affects an unknown part. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Heap-based buffer overflow in the Recovery Mode component in Apple iPhone OS before 3.1, and iPhone OS before 3.1.1 for iPod touch, allows local users to bypass the passcode requirement and access arbitrary data via vectors related to "command parsing."
The weakness was released 09/10/2009 with Apple as HT3860 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is uniquely identified as CVE-2009-2795 since 08/17/2009. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 1.0.1 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (53183), SecurityFocus (BID 36341†), Secunia (SA36677†) and Vulnerability Center (SBV-47668†). Entries connected to this vulnerability are available at VDB-3995, VDB-49945, VDB-49943 and VDB-49942. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Support
Website
- Vendor: https://www.apple.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.3VulDB Meta Temp Score: 8.9
VulDB Base Score: 9.3
VulDB Temp Score: 8.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: Memory corruptionCWE: CWE-119
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: iPhone OS 1.0.1
Timeline
08/17/2009 🔍09/09/2009 🔍
09/09/2009 🔍
09/10/2009 🔍
09/10/2009 🔍
12/17/2014 🔍
03/18/2015 🔍
06/15/2017 🔍
Sources
Vendor: apple.comAdvisory: HT3860
Organization: Apple
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2009-2795 (🔍)
GCVE (CVE): GCVE-0-2009-2795
GCVE (VulDB): GCVE-100-49941
X-Force: 53183
SecurityFocus: 36341 - Apple iPhone and iPod Touch Recovery Mode Command Parsing Heap Buffer Overflow Vulnerability
Secunia: 36677
Vulnerability Center: 47668 - Apple iOS Before 3.1 Local Security Bypass via Vectors Related to Command Parsing, Medium
See also: 🔍
Entry
Created: 03/18/2015 15:15Updated: 06/15/2017 11:39
Changes: 03/18/2015 15:15 (59), 06/15/2017 11:39 (5)
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.