| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Apple iPhone OS up to 2.2.1. It has been classified as problematic. Impacted is an unknown function of the component Telephony. Performing a manipulation results in denial of service. This vulnerability is cataloged as CVE-2009-1683. There is no exploit available.
Details
A vulnerability was found in Apple iPhone OS up to 2.2.1 (Smartphone Operating System). It has been classified as critical. This affects an unknown code block of the component Telephony. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. The summary by CVE is:
The Telephony component in Apple iPhone OS 1.0 through 2.2.1 and iPhone OS for iPod touch 1.1 through 2.2.1 allows remote attackers to cause a denial of service (device reset) via a crafted ICMP echo request, which triggers an assertion error related to a "logic issue."
The weakness was shared 06/19/2009 by Thomas Adams (Oliver) as HT3639 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is uniquely identified as CVE-2009-1683 since 05/20/2009. The exploitability is told to be easy. 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.
It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (51214), SecurityFocus (BID 35414†) and Vulnerability Center (SBV-47655†). The entries VDB-48670, VDB-48668, VDB-48667 and VDB-48666 are related to this item. 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: 7.5VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.5
VulDB Temp Score: 7.1
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: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/20/2009 🔍06/17/2009 🔍
06/17/2009 🔍
06/19/2009 🔍
06/19/2009 🔍
12/17/2014 🔍
03/17/2015 🔍
06/15/2017 🔍
Sources
Vendor: apple.comAdvisory: HT3639
Researcher: Thomas Adams (Oliver)
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2009-1683 (🔍)
GCVE (CVE): GCVE-0-2009-1683
GCVE (VulDB): GCVE-100-48669
X-Force: 51214
SecurityFocus: 35414 - RETIRED: Apple iPhone and iPod touch Prior to Version 3.0 Multiple Vulnerabilities
Vulnerability Center: 47655 - Apple iOS 1.0 Through 2.2.1 Remote DoS due to an Assertion Error, High
Vupen: ADV-2009-1621
See also: 🔍
Entry
Created: 03/17/2015 23:38Updated: 06/15/2017 11:37
Changes: 03/17/2015 23:38 (57), 06/15/2017 11:37 (7)
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.