CVE-2007-3108

LOWCVSS v2 · 1.21.2—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 1.2 — v2 rates that LOW (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:L/AC:H/Au:N/C:P/I:N/A:N. 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 0.4% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
1.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS v2: 1.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The BN_from_montgomery function in crypto/bn/bn_mont.c in OpenSSL 0.9.8e and earlier does not properly perform Montgomery multiplication, which might allow local users to conduct a side-channel attack and retrieve RSA private keys.

CVSS v2.0 (legacy)
1.2LOWNVD never assigned a CVSS v3 rating to this CVE
EG Score
1.2LOWlow confidence
EG Risk
10
EG Risk 10/100CISA SSVC

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
Severity12% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 8, 2007

Last Modified

April 23, 2026

References (92)

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibssl0.9.8 (0.9.8c-4ubuntu0.1) @ feisty2026-05-31ubuntu
redhatopenssl-0:0.9.7a-43.17.el4_6.12007-11-15redhat
redhatopenssl-0:0.9.7a-33.242007-10-22redhat
redhatopenssl-0:0.9.8b-8.3.el5_0.22007-10-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 0.9.8e-6: fixed in 0.9.8e-6
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 0.9.8e-6: fixed in 0.9.8e-6
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 0.9.8e-6: fixed in 0.9.8e-6
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 0.9.8e-6: fixed in 0.9.8e-6
—
Debian:4.0(1)
PackageVulnerable rangeFix by version rangeDependents
openssl0.9.8c-4, 0.9.8c-4etch1, 0.9.8c-4etch2
  • every version up to 0.9.8c-4etch3: fixed in 0.9.8c-4etch3
—

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 136 total refreshes for this CVE.

  1. 2026-10-09 20:00 UTCEPSS rescore
  2. 2026-10-08 16:33 UTCEPSS rescore
  3. 2026-10-07 23:37 UTCEPSS rescore
  4. 2026-10-06 15:09 UTCEPSS rescore
  5. 2026-10-05 17:37 UTCEPSS rescore
  6. 2026-10-04 23:15 UTCEPSS rescore
  7. 2026-10-04 11:01 UTCOSV refresh
  8. 2026-10-03 14:20 UTCEPSS rescore
  9. 2026-10-01 19:42 UTCEPSS rescore
  10. 2026-09-30 14:57 UTCEPSS rescore
  11. 2026-09-29 07:41 UTCEG score recompute
  12. 2026-09-18 19:20 UTCEPSS rescore
  13. 2026-09-17 19:20 UTCEPSS rescore
  14. 2026-09-15 03:04 UTCEPSS rescore
  15. 2026-09-15 01:14 UTCOSV refresh
  16. 2026-09-12 14:54 UTCEPSS rescore
  17. 2026-09-05 15:22 UTCEPSS rescore
  18. 2026-09-04 13:55 UTCEPSS rescore
  19. 2026-09-04 04:59 UTCEPSS rescore
  20. 2026-08-30 01:14 UTCEPSS rescore
  21. 2026-08-27 00:37 UTCOSV refresh
  22. 2026-08-10 14:38 UTCOSV refresh
  23. 2026-08-08 16:30 UTCEPSS rescore
  24. 2026-08-07 16:20 UTCEPSS rescore
  25. 2026-08-06 13:41 UTCEPSS rescore
Show 75 more
  1. 2026-08-05 19:11 UTCEPSS rescore
  2. 2026-08-04 15:03 UTCEPSS rescore
  3. 2026-08-03 10:28 UTCEPSS rescore
  4. 2026-07-30 16:22 UTCEPSS rescore
  5. 2026-07-30 01:25 UTCEPSS rescore
  6. 2026-07-28 15:30 UTCEPSS rescore
  7. 2026-07-26 13:32 UTCEG score recompute▲ 1.20
  8. 2026-07-25 15:30 UTCOSV refresh
  9. 2026-07-25 14:12 UTCEPSS rescore
  10. 2026-07-24 14:11 UTCEPSS rescore
  11. 2026-07-23 14:13 UTCEPSS rescore
  12. 2026-07-23 00:53 UTCEG score recompute
  13. 2026-07-23 00:32 UTCEG score recompute
  14. 2026-07-22 23:58 UTCEG score recompute
  15. 2026-07-22 21:37 UTCEG score recompute
  16. 2026-07-22 14:03 UTCEPSS rescore
  17. 2026-07-21 15:19 UTCEPSS rescore
  18. 2026-07-20 17:03 UTCEPSS rescore
  19. 2026-07-18 09:59 UTCEPSS rescore
  20. 2026-07-16 16:58 UTCEPSS rescore
  21. 2026-07-15 16:54 UTCEPSS rescore
  22. 2026-07-15 16:54 UTCEPSS rescore
  23. 2026-07-15 01:55 UTCEPSS rescore
  24. 2026-07-13 06:07 UTCEPSS rescore
  25. 2026-07-11 08:22 UTCEPSS rescore
  26. 2026-07-08 15:09 UTCEPSS rescore
  27. 2026-07-08 10:05 UTCOSV refresh
  28. 2026-07-06 16:22 UTCEPSS rescore
  29. 2026-07-06 02:19 UTCEPSS rescore
  30. 2026-07-05 02:26 UTCEPSS rescore
  31. 2026-07-04 06:27 UTCEPSS rescore
  32. 2026-07-04 06:27 UTCEPSS rescore
  33. 2026-07-02 14:00 UTCEPSS rescore
  34. 2026-07-01 15:02 UTCEPSS rescore
  35. 2026-07-01 15:02 UTCEPSS rescore
  36. 2026-06-30 23:19 UTCEPSS rescore
  37. 2026-06-30 23:19 UTCEPSS rescore
  38. 2026-06-29 14:02 UTCEPSS rescore
  39. 2026-06-29 14:02 UTCEPSS rescore
  40. 2026-06-28 14:03 UTCEPSS rescore
  41. 2026-06-28 04:52 UTCEPSS rescore
  42. 2026-06-27 03:04 UTCEPSS rescore
  43. 2026-06-25 13:46 UTCEPSS rescore
  44. 2026-06-25 13:46 UTCEPSS rescore
  45. 2026-06-24 14:02 UTCEPSS rescore
  46. 2026-06-24 14:02 UTCEPSS rescore
  47. 2026-06-23 21:29 UTCEPSS rescore
  48. 2026-06-23 21:29 UTCEPSS rescore
  49. 2026-06-22 14:22 UTCEPSS rescore
  50. 2026-06-21 14:53 UTCEPSS rescore
  51. 2026-06-21 01:56 UTCEPSS rescore
  52. 2026-06-21 01:56 UTCEPSS rescore
  53. 2026-06-19 22:06 UTCOSV refresh
  54. 2026-06-19 19:22 UTCEPSS rescore
  55. 2026-06-19 19:22 UTCEPSS rescore
  56. 2026-06-18 17:49 UTCEPSS rescore
  57. 2026-06-18 17:49 UTCEPSS rescore
  58. 2026-06-17 17:49 UTCEPSS rescore
  59. 2026-06-17 17:49 UTCEPSS rescore
  60. 2026-06-16 17:49 UTCEPSS rescore
  61. 2026-06-16 17:49 UTCEPSS rescore
  62. 2026-06-16 17:49 UTCEPSS rescore
  63. 2026-06-15 17:44 UTCEPSS rescore
  64. 2026-06-13 22:57 UTCEPSS rescore
  65. 2026-06-12 23:08 UTCEPSS rescore
  66. 2026-06-10 22:14 UTCEPSS rescore
  67. 2026-06-10 13:17 UTCEPSS rescore
  68. 2026-06-08 14:13 UTCEPSS rescore
  69. 2026-06-07 15:21 UTCEPSS rescore
  70. 2026-06-06 13:44 UTCEPSS rescore
  71. 2026-06-06 13:44 UTCEPSS rescore
  72. 2026-06-05 22:44 UTCEPSS rescore
  73. 2026-06-05 22:44 UTCEPSS rescore
  74. 2026-06-05 06:07 UTCEPSS rescore
  75. 2026-06-04 13:09 UTCEPSS rescore

Related CVEs(same product + same vendor)

Same vendor

2 shown

redhat:RHSA-2007:0813 · redhat:RHSA-2007:0964

Frequently asked(4)

What is CVE-2007-3108?
CVE-2007-3108 is a low vulnerability published on August 8, 2007. The BNfrommontgomery function in crypto/bn/bn_mont.c in OpenSSL 0.9.8e and earlier does not properly perform Montgomery multiplication, which might allow local users to conduct a side-channel attack and retrieve RSA private keys.
When was CVE-2007-3108 disclosed?
CVE-2007-3108 was first published on August 8, 2007, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2007-3108 actively exploited?
CVE-2007-3108 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
How do I remediate CVE-2007-3108?
A fix for CVE-2007-3108 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2007-3108

Explore →

Is Your Infrastructure Affected by CVE-2007-3108?

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

Book a Demo →Browse All CVEs