CVE-2011-0142

HIGHCVSS v2 · 7.67.6
EchelonGraph scoreLOW confidence

“—” beside the score: it is equal to NVD's CVSS v2 base score.

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.6 — NVD rates that HIGH (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:H/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 2.6% exploitation probability in the next 30 days; it does not lift the v2 base. EPSS sets EG Risk's exploitation input. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
7.6EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.6%CVSS v2: 7.6Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

WebKit, as used in Apple iTunes before 10.2 on Windows, allows man-in-the-middle attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via vectors related to iTunes Store browsing, a different vulnerability than other CVEs listed in APPLE-SA-2011-03-02-1.

CVSS v2.0 (legacy)
7.6HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.6HIGHlow confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
The EG Score, 7.6 of 10.
Exploitation2.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
2.6%
EPSS %ILE
85th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 3, 2011

Last Modified

April 29, 2026

References (7)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 19× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 79 of 115 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 21 repeat rows among the latest 100 are merged into the row they repeat. The 36 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 01:45 UTCEG score recompute
  2. 2026-10-11 13:38 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  3. 2026-10-10 19:54 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  4. 2026-10-09 20:00 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  5. 2026-10-08 16:34 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  6. 2026-10-07 23:38 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  7. 2026-10-06 15:10 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  8. 2026-10-05 17:37 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  9. 2026-10-04 23:16 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  10. 2026-09-30 14:58 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  11. 2026-09-29 08:14 UTCEG score recompute
  12. 2026-09-27 13:39 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  13. 2026-09-26 15:52 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  14. 2026-09-24 13:57 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  15. 2026-09-20 20:08 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  16. 2026-09-16 13:58 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  17. 2026-09-15 03:04 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  18. 2026-09-13 16:40 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  19. 2026-09-12 14:54 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  20. 2026-09-06 13:41 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  21. 2026-09-05 15:22 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  22. 2026-09-04 13:55 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  23. 2026-08-25 13:43 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  24. 2026-08-19 16:58 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  25. 2026-08-18 13:42 UTCEPSS rescoreEPSS 2.6% · 84th percentile
Show 54 more
  1. 2026-08-15 01:25 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  2. 2026-08-09 13:41 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  3. 2026-08-08 16:31 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  4. 2026-08-06 13:41 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  5. 2026-08-05 19:12 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  6. 2026-08-04 15:04 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  7. 2026-08-01 04:10 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  8. 2026-07-30 01:26 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  9. 2026-07-26 13:42 UTCEG score recomputeFirst assessed: 7.6 HIGH
  10. 2026-07-23 14:14 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  11. 2026-07-23 01:04 UTCEG score recompute
  12. 2026-07-23 00:39 UTCEG score recompute
  13. 2026-07-23 00:07 UTCEG score recompute
  14. 2026-07-22 21:46 UTCEG score recompute
  15. 2026-07-22 14:03 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  16. 2026-07-21 15:21 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  17. 2026-07-20 17:03 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  18. 2026-07-19 02:25 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  19. 2026-07-18 10:00 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  20. 2026-07-16 16:58 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  21. 2026-07-15 16:54 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  22. 2026-07-15 01:55 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  23. 2026-07-13 22:25 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  24. 2026-07-13 06:08 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  25. 2026-07-11 08:22 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  26. 2026-07-08 15:10 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  27. 2026-07-06 16:23 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  28. 2026-07-06 02:19 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  29. 2026-07-05 02:26 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  30. 2026-07-04 06:27 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  31. 2026-07-02 14:01 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  32. 2026-07-01 15:02 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  33. 2026-06-30 23:19 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  34. 2026-06-28 14:03 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  35. 2026-06-28 04:52 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  36. 2026-06-27 03:05 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  37. 2026-06-25 13:46 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  38. 2026-06-24 14:02 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  39. 2026-06-23 21:30 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  40. 2026-06-19 19:22 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  41. 2026-06-18 17:49 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  42. 2026-06-17 17:49 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  43. 2026-06-16 17:49 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  44. 2026-06-15 17:44 UTCEPSS rescoreEPSS 2.6% · 83rd percentile
  45. 2026-06-14 23:14 UTCEPSS rescoreEPSS 0.6% · 69th percentile
  46. 2026-06-13 22:57 UTCEPSS rescoreEPSS 0.6% · 69th percentile
  47. 2026-06-12 23:08 UTCEPSS rescoreEPSS 0.6% · 69th percentile
  48. 2026-06-11 13:56 UTCEPSS rescoreEPSS 0.6% · 69th percentile
  49. 2026-06-10 22:14 UTCEPSS rescoreEPSS 0.6% · 69th percentile
  50. 2026-06-10 13:17 UTCEPSS rescoreEPSS 0.6% · 69th percentile
  51. 2026-06-08 14:14 UTCEPSS rescoreEPSS 0.6% · 69th percentile
  52. 2026-06-07 15:22 UTCEPSS rescoreEPSS 0.6% · 69th percentile
  53. 2026-06-06 13:44 UTCEPSS rescoreEPSS 0.6% · 69th percentile
  54. 2026-06-05 22:44 UTCEPSS rescoreEPSS 0.6% · 69th percentile

Frequently asked(4)

What is CVE-2011-0142?
CVE-2011-0142 is a high-severity vulnerability; its CVE record was published on March 3, 2011. WebKit, as used in Apple iTunes before 10.2 on Windows, allows man-in-the-middle attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via vectors related to iTunes Store browsing, a different vulnerability than other CVEs listed in…
When was CVE-2011-0142 made public?
CVE-2011-0142 was made public on March 2, 2011: that is the date its CVE record's CNA, Apple Inc., gives for when the vulnerability was made public. The CVE record itself was published on March 3, 2011. EchelonGraph's copy of the record carries a last-modified date of April 29, 2026; the record at its source may have been updated since.
Is CVE-2011-0142 actively exploited?
CVE-2011-0142 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% probability of exploitation in the next 30 days (85th percentile of EPSS-scored CVEs).
How do I remediate CVE-2011-0142?
A fix for CVE-2011-0142 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2011-0142

Explore →

Is Your Infrastructure Affected by CVE-2011-0142?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.