CVE-2011-4121

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-04-22. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 3%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The OpenSSL extension of Ruby (Git trunk) versions after 2011-09-01 up to 2011-11-03 always generated an exponent value of '1' to be used for private RSA key generation. A remote attacker could use this flaw to bypass or corrupt integrity of services, depending on strong private RSA keys generation mechanism.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
83.0%
KEV
Not listed

Published

November 26, 2019

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Jun 7, 2026
Patch available. Sources: redhat.
generic

CVE-2011-4121

https://security-tracker.debian.org/tracker/CVE-2011-4121
redhat

751800 – (CVE-2011-4121) CVE-2011-4121 ruby (openssl extension): Insecure way of creation exponent value by private RSA key generation

Affected: Red Hat Enterprise Linux 4, 5, and 6, since those versions directly call RSA_generate_key(3) OpenSSL library routine for RSA k

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-4121
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/cve-2011-4121
generic

oss-security - CVE-2013-2228 : Salt Stack RSA exponent of 1 (there can be only one! da-na-naaah! na-na-na-naahh-nah-nahhh!)

http://www.openwall.com/lists/oss-security/2013/07/01/1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 43× 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.

  1. 2026-07-11 08:22 UTCEPSS rescore
  2. 2026-07-11 08:22 UTCEPSS rescore
  3. 2026-07-08 15:10 UTCEPSS rescore
  4. 2026-07-08 15:10 UTCEPSS rescore
  5. 2026-07-06 16:23 UTCEPSS rescore
  6. 2026-07-06 02:19 UTCEPSS rescore
  7. 2026-07-06 02:19 UTCEPSS rescore
  8. 2026-07-05 02:26 UTCEPSS rescore
  9. 2026-07-04 06:27 UTCEPSS rescore
  10. 2026-07-02 14:01 UTCEPSS rescore
  11. 2026-07-01 15:02 UTCEPSS rescore
  12. 2026-07-01 15:02 UTCEPSS rescore
  13. 2026-06-30 23:19 UTCEPSS rescore
  14. 2026-06-30 23:19 UTCEPSS rescore
  15. 2026-06-29 14:02 UTCEPSS rescore
  16. 2026-06-28 14:03 UTCEPSS rescore
  17. 2026-06-28 04:53 UTCEPSS rescore
  18. 2026-06-28 04:52 UTCEPSS rescore
  19. 2026-06-27 03:05 UTCEPSS rescore
  20. 2026-06-27 03:05 UTCEPSS rescore
  21. 2026-06-25 13:46 UTCEPSS rescore
  22. 2026-06-24 14:02 UTCEPSS rescore
  23. 2026-06-24 14:02 UTCEPSS rescore
  24. 2026-06-23 21:30 UTCEPSS rescore
  25. 2026-06-23 21:30 UTCEPSS rescore
Show 54 more
  1. 2026-06-22 14:22 UTCEPSS rescore
  2. 2026-06-22 14:22 UTCEPSS rescore
  3. 2026-06-21 01:56 UTCEPSS rescore
  4. 2026-06-21 01:56 UTCEPSS rescore
  5. 2026-06-19 19:22 UTCEPSS rescore
  6. 2026-06-19 19:22 UTCEPSS rescore
  7. 2026-06-18 17:49 UTCEPSS rescore
  8. 2026-06-18 17:49 UTCEPSS rescore
  9. 2026-06-17 17:49 UTCEPSS rescore
  10. 2026-06-17 17:49 UTCEPSS rescore
  11. 2026-06-17 17:49 UTCEPSS rescore
  12. 2026-06-16 17:49 UTCEPSS rescore
  13. 2026-06-15 17:44 UTCEPSS rescore
  14. 2026-06-14 23:14 UTCEPSS rescore
  15. 2026-06-14 23:14 UTCEPSS rescore
  16. 2026-06-13 22:57 UTCEPSS rescore
  17. 2026-06-13 22:57 UTCEPSS rescore
  18. 2026-06-12 23:08 UTCEPSS rescore
  19. 2026-06-11 13:56 UTCEPSS rescore
  20. 2026-06-10 22:14 UTCEPSS rescore
  21. 2026-06-10 13:17 UTCEPSS rescore
  22. 2026-06-08 14:14 UTCEPSS rescore
  23. 2026-06-08 14:14 UTCEPSS rescore
  24. 2026-06-07 15:22 UTCEPSS rescore
  25. 2026-06-07 15:22 UTCEPSS rescore
  26. 2026-06-06 13:45 UTCEPSS rescore
  27. 2026-06-06 13:44 UTCEPSS rescore
  28. 2026-06-05 22:44 UTCEPSS rescore
  29. 2026-06-05 06:08 UTCEPSS rescore
  30. 2026-06-05 06:07 UTCEPSS rescore
  31. 2026-06-04 13:09 UTCEPSS rescore
  32. 2026-06-04 13:09 UTCEPSS rescore
  33. 2026-06-02 20:10 UTCEPSS rescore
  34. 2026-06-02 20:10 UTCEPSS rescore
  35. 2026-06-01 13:49 UTCEPSS rescore
  36. 2026-06-01 13:49 UTCEPSS rescore
  37. 2026-05-31 22:28 UTCEPSS rescore
  38. 2026-05-31 22:28 UTCEPSS rescore
  39. 2026-05-31 00:14 UTCEPSS rescore
  40. 2026-05-31 00:14 UTCEPSS rescore
  41. 2026-05-29 13:41 UTCEPSS rescore
  42. 2026-05-29 13:40 UTCEPSS rescore
  43. 2026-05-28 13:42 UTCEPSS rescore
  44. 2026-05-28 13:42 UTCEPSS rescore
  45. 2026-05-28 13:42 UTCEPSS rescore
  46. 2026-05-27 13:38 UTCEPSS rescore
  47. 2026-05-27 13:38 UTCEPSS rescore
  48. 2026-05-27 11:09 UTCEG score recompute
  49. 2026-05-27 11:09 UTCGHSA enrichment
  50. 2026-05-26 13:41 UTCEPSS rescore
  51. 2026-05-26 13:41 UTCEPSS rescore
  52. 2026-05-26 07:16 UTCEPSS rescore
  53. 2026-05-26 07:16 UTCEPSS rescore
  54. 2026-05-24 16:43 UTCEPSS rescore

Frequently asked(5)

What is CVE-2011-4121?
CVE-2011-4121 is a critical vulnerability published on November 26, 2019. The OpenSSL extension of Ruby (Git trunk) versions after 2011-09-01 up to 2011-11-03 always generated an exponent value of '1' to be used for private RSA key generation. A remote attacker could use this flaw to bypass or corrupt integrity of services, depending on strong private RSA keys generation…
When was CVE-2011-4121 disclosed?
CVE-2011-4121 was first published in the National Vulnerability Database on November 26, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2011-4121 actively exploited?
CVE-2011-4121 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 83.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2011-4121?
CVE-2011-4121 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2011-4121?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2011-4121, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2011-4121?

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

Start Free Scan →Browse All CVEs