Infinite loop in BN_mod_sqrt() reachable when parsing certificates
Noroxi assessment
Priority: Plan (action score 52/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 73.1% (FIRST EPSS); higher than 99.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: compat-openssl10 (AlmaLinux:8) 1:1.0.2o-4.el8_6; openssl (AlmaLinux:8) 1:1.1.1k-6.el8_5; openssl-devel (AlmaLinux:8) 1:1.1.1k-6.el8_5.
- Mentioned 6 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Add it to your regular patch cycle. Upgrade to compat-openssl10 (AlmaLinux:8) 1:1.0.2o-4.el8_6; openssl (AlmaLinux:8) 1:1.1.1k-6.el8_5; openssl-devel (AlmaLinux:8) 1:1.1.1k-6.el8_5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc).
- BDU:2022-01315
- GHSA-x3mh-jvjw-3xwx
- ALSA-2022:1065
- ALSA-2022:5326
- DLA-2952-1
- DLA-2953-1
- DSA-5103-1
- openSUSE-SU-2022:0856-1
- openSUSE-SU-2024:11927-1
- openSUSE-SU-2024:11933-1
- openSUSE-SU-2024:11944-1
- openSUSE-SU-2024:11953-1
- openSUSE-SU-2024:12444-1
- openSUSE-SU-2025:14965-1
- RHSA-2022:1065
- RHSA-2022:1066
- RHSA-2022:1071
- RHSA-2022:1073
- RHSA-2022:1076
- RHSA-2022:1077
- Published
- Mar 15, 2022
- Updated
- Jun 17, 2026
- EPSS
- 73.2% · 99th percentile
- CWE
- CWE-835
Report tools
Action score
52
Plan
Add it to your regular patch cycle.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 22 / 30 · 73.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| netapp | cloud volumes ontap mediator | cpe:2.3:a:netapp:cloud_volumes_ontap_mediator |
| netapp | clustered data ontap | cpe:2.3:a:netapp:clustered_data_ontap |
| netapp | clustered data ontap antivirus connector | cpe:2.3:a:netapp:clustered_data_ontap_antivirus_connector |
| netapp | santricity smi-s provider | cpe:2.3:a:netapp:santricity_smi-s_provider |
| netapp | storagegrid | cpe:2.3:a:netapp:storagegrid |
| netapp | a250 firmware | cpe:2.3:o:netapp:a250_firmware |
| netapp | a250 | cpe:2.3:h:netapp:a250 |
| netapp | 500f firmware | cpe:2.3:o:netapp:500f_firmware |
| netapp | 500f | cpe:2.3:h:netapp:500f |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
and 3 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs node.js12.0.0 and later · up to 12.12.0 inclusive
- nodejs node.js12.13.0 and later · before 12.22.11
- nodejs node.jsafter 14.0.0 · up to 14.14.0 inclusive
- nodejs node.js14.15.0 and later · before 14.19.1
- nodejs node.jsafter 16.0.0 · up to 16.12.0 inclusive
- nodejs node.js16.13.0 and later · before 16.14.2
- nodejs node.jsafter 17.0.0 · before 17.7.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.
OpenSSL OpenSSL
- Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1), Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m), Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc)affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | compat-openssl10 | before 1:1.0.2o-4.el8_6 | 1:1.0.2o-4.el8_6 |
| AlmaLinux:8 | openssl | before 1:1.1.1k-6.el8_5 | 1:1.1.1k-6.el8_5 |
| AlmaLinux:8 | openssl-devel | before 1:1.1.1k-6.el8_5 | 1:1.1.1k-6.el8_5 |
| AlmaLinux:8 | openssl-libs | before 1:1.1.1k-6.el8_5 | 1:1.1.1k-6.el8_5 |
| AlmaLinux:8 | openssl-perl | before 1:1.1.1k-6.el8_5 | 1:1.1.1k-6.el8_5 |
| Alpine:v3.12 | openssl | from 1.0.2 · before 1.1.1n-r0 | 1.1.1n-r0 |
| Alpine:v3.14 | libretls | before 3.3.3p1-r3 | 3.3.3p1-r3 |
| Alpine:v3.15 | libretls | before 3.3.4-r3 | 3.3.4-r3 |
| Alpine:v3.15 | openssl3 | before 3.0.2-r0 | 3.0.2-r0 |
| Alpine:v3.16 | libretls | before 3.5.1-r0 | 3.5.1-r0 |
| Alpine:v3.17 | openssl | from 1.0.2 · before 3.0.2-r0 | 3.0.2-r0 |
| crates.io | openssl-src | from 0.0.0-0 · before 111.18.0 | 111.18.0 |
| crates.io | openssl-src | from 300.0.0 · before 300.0.5 | 300.0.5 |
| crates.io | openssl-src | before 111.18.0 | 111.18.0 |
| Debian:10 | openssl | before 1.1.1d-0+deb10u8 | 1.1.1d-0+deb10u8 |
| Debian:11 | openssl | before 1.1.1k-1+deb11u2 | 1.1.1k-1+deb11u2 |
| Debian:12 | openssl | before 1.1.1n-1 | 1.1.1n-1 |
| Debian:9 | openssl | before 1.1.0l-1~deb9u5 | 1.1.0l-1~deb9u5 |
| Debian:9 | openssl1.0 | before 1.0.2u-1~deb9u7 | 1.0.2u-1~deb9u7 |
| openSUSE:Leap 15.3 | openssl-1_0_0 | before 1.0.2p-3.49.1 | 1.0.2p-3.49.1 |
| openSUSE:Tumbleweed | cargo-audit-advisory-db | before 20220323-1.1 | 20220323-1.1 |
| openSUSE:Tumbleweed | libressl | before 3.4.3-1.1 | 3.4.3-1.1 |
| openSUSE:Tumbleweed | openssl-1_1 | before 1.1.1n-1.1 | 1.1.1n-1.1 |
| openSUSE:Tumbleweed | openssl-3 | before 3.0.2-1.1 | 3.0.2-1.1 |
+96
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code 65This week
- CVE-2016-2108The ASN.1 implementation in OpenSSL before 1.0.1o and 1.0.2 before 1.0.2c allows remote attackers to execute arbitrary code or cause a denia62This week
- CVE-2016-6309statem/statem.c in OpenSSL 1.1.0a does not consider memory-block movement after a realloc call, which allows remote attackers to cause a den60This week
- CVE-2022-3786X.509 Email Address Variable Length Buffer Overflow58Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:compat-openssl10 | 1:1.0.2o-4.el8_6 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:openssl | 1:1.1.1k-6.el8_5 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:openssl-devel | 1:1.1.1k-6.el8_5 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:openssl-libs | 1:1.1.1k-6.el8_5 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:openssl-perl | 1:1.1.1k-6.el8_5 · AlmaLinux:8 | Package registry (OSV) |
| alpine:libretls | 3.3.3p1-r3 · Alpine:v3.14 | Package registry (OSV) |
| alpine:openssl | 1.1.1n-r0 · Alpine:v3.12 | Package registry (OSV) |
| alpine:openssl3 | 3.0.2-r0 · Alpine:v3.15 | Package registry (OSV) |
| crates.io:openssl-src | 111.18.0 | Package registry (OSV) |
| crates.io:openssl-src | 300.0.5 | Package registry (OSV) |
| debian:openssl | 1.1.1n-1 · Debian:12 | Package registry (OSV) |
| debian:openssl1.0 | 1.0.2u-1~deb9u7 · Debian:9 | Package registry (OSV) |
| opensuse:cargo-audit-advisory-db | 20220323-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:libressl | 3.4.3-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:nodejs12 | 12.22.12-150200.4.32.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:nodejs14 | 14.19.1-150200.15.31.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:openssl-1_0_0 | 1.0.2p-3.49.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:openssl-1_1 | 1.1.1n-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:openssl-3 | 3.0.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:python-ecdsa | 0.18.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:jbcs-httpd24-apr-util | 0:1.6.1-91.jbcs.el7 · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr-util-debuginfo | 0:1.6.1-91.jbcs.el7 · Red Hat:jboss_core_services:1::el7 | Package registry (OSV) |
| red hat:openssl | 1:1.1.1k-6.el8_5 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:openssl-debuginfo | 1:1.1.1k-6.el8_5 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:openssl-debugsource | 1:1.1.1k-6.el8_5 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:openssl-devel | 1:1.1.1k-6.el8_5 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:openssl-libs | 1:1.1.1k-6.el8_5 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:openssl-libs-debuginfo | 1:1.1.1k-6.el8_5 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:openssl-perl | 1:1.1.1k-6.el8_5 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:openssl-static | 1:1.0.2k-25.el7_9 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
+17
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×6
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:181 | 2022-03-15 |
| Proof-of-concept repository on GitHub | stars:9 | 2022-04-04 |
| Proof-of-concept repository on GitHub | stars:11 | 2022-04-18 |
| Proof-of-concept repository on GitHub | stars:2 | 2022-04-21 |
| Proof-of-concept repository on GitHub | stars:0 | 2023-09-11 |
| Proof-of-concept repository on GitHub | stars:1 | 2023-10-26 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-1 d
- Published
- TodayOct 13, 2026+1673 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-22-0552 · Aug 15, 2022(RedHat Güvenlik Güncellemesi)
- TR-22-0537 · Aug 10, 2022( Mitsubishi Electric Zafiyeti)
- TR-22-0515 · Aug 1, 2022(IBM Güvenlik Zafiyeti)
- TR-22-0474 · Jul 4, 2022(RedHat Güvenlik Güncellemesi)
- TR-22-0436 · Jun 20, 2022(IBM Güvenlik Bildirimi)
- TR-22-0433 · Jun 17, 2022(Siemens Endüstriyel Ürünler Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- seclists.org/fulldisclosure/2022/May/33
- seclists.org/fulldisclosure/2022/May/35
- seclists.org/fulldisclosure/2022/May/38
- cert-portal.siemens.com/productcert/pdf/ssa-712929.pdf
- git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=3118eb64934499d93db3230748a452351d1d9a65
- git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=380085481c64de749a6dd25cdf0bcf4360b30f83
- git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=a466912611aa6cbdf550cd10601390e587451246
- lists.debian.org/debian-lts-announce/2022/03/msg00023.html
- lists.debian.org/debian-lts-announce/2022/03/msg00024.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/323SNN6ZX7PRJJWP2BUAFLPUAE42XWLZ/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GDB3GQVJPXJE7X5C5JN6JAA4XUDWD6E6/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/W6K3PR542DXWLEFFMFIDMME4CWMHJRMG/
- psirt.global.sonicwall.com/vuln-detail/SNWLID-2022-0002
- security.gentoo.org/glsa/202210-02
- security.netapp.com/advisory/ntap-20220321-0002/
- security.netapp.com/advisory/ntap-20220429-0005/
- security.netapp.com/advisory/ntap-20240621-0006/
- support.apple.com/kb/HT213255
- support.apple.com/kb/HT213256
Vendor advisories and official records. Exploit/PoC links are deliberately left out.