SecOps SignalSecurity Intelligence Workspace
Collection Degraded30 / 46 Sources HealthyPublic Intel Only
Vulnerabilities/CVE-2022-0778Public Intelligence Dossier
Source: openssl · Limited verification•Last verified: •Collection Degraded
CVE-2022-0778Unknown / EvaluatingHIGH (raw)CVSS 7.5CWE-835

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

Published: 15 Mar 2022•Last updated: 14 Oct 2026, 06:47 PM IST•Source identifier: openssl-security@openssl.org
Dossier completeness: source-provided sections 2 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Unknown
KEV status was not determined.
CVSS score
7.5HIGH (raw)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Metric sourcenvd@nist.gov
EPSS probability
73.2%0.732
Percentile99th
Weakness type
CWE-835
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

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).

SOC priority

High

Actively exploited

Unknown

Publicly disclosed

Unknown

Risk basis: SOC ecosystem technology relevance; HIGH severity; No confirmed exploitation signal in current enrichment

Affected Products & Remediation

13 source-backed products
Affected products and versions (source)
  • openssl openssl · >= 1.0.2 < 1.0.2zd; >= 1.1.0 < 1.1.1n; >= 3.0.0 < 3.0.2 · NVD CPE · Source
  • debian debian linux · 9.0; 10.0; 11.0 · NVD CPE · Source
  • netapp cloud volumes ontap mediator · version range not provided by source · NVD CPE · Source
  • netapp clustered data ontap · version range not provided by source · NVD CPE · Source
  • netapp clustered data ontap antivirus connector · version range not provided by source · NVD CPE · Source
  • netapp santricity smi-s provider · version range not provided by source · NVD CPE · Source
  • netapp storagegrid · version range not provided by source · NVD CPE · Source
  • netapp a250 firmware · version range not provided by source · NVD CPE · Source
  • netapp 500f firmware · version range not provided by source · NVD CPE · Source
  • fedoraproject fedora · 34; 36 · NVD CPE · Source
  • tenable nessus · < 8.15.4; >= 10.0.0 < 10.1.2 · NVD CPE · Source
  • mariadb mariadb · >= 10.2.0 < 10.2.42; >= 10.3.0 < 10.3.33; >= 10.4.0 < 10.4.23; >= 10.5.0 < 10.5.14; >= 10.6.0 < 10.6.6; >= 10.7.0 < 10.7.2 · NVD CPE · Source
  • nodejs node.js · >= 12.0.0 <= 12.12.0; >= 12.13.0 < 12.22.11; > 14.0.0 <= 14.14.0; >= 14.15.0 < 14.19.1; > 16.0.0 <= 16.12.0; >= 16.13.0 < 16.14.2; > 17.0.0 < 17.7.2 · NVD CPE · Source
NVD applicability prerequisites: cpe:2.3:h:netapp:a250:-:*:*:*:*:*:*:*, cpe:2.3:h:netapp:500f:-:*:*:*:*:*:*:*. These are conditions, not proof that an environment is exposed or unaffected.
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

Not provided by source

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Unknown
Exploited (source statement)
Unknown
Publicly disclosed (source)
Unknown

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched network-unauthenticated (CVSS AV:N, CVSS PR:N, CVSS UI:N)

Exposure

  1. Identify devices reporting this CVE and note which expose the affected service to untrusted networks.Telemetry: DeviceTvmSoftwareVulnerabilities · A network-reachable, no-privilege vector makes internet-facing instances the first exposure question. · Rule network-unauthenticated

Exploitation evidence

  1. Review inbound connections to the affected service from unexpected sources since the advisory date.Telemetry: DeviceNetworkEvents · Hunting hypothesis from the CVSS vector; it does not show that exploitation occurred. · Rule network-unauthenticated

Response

  1. Confirm the source-stated update is installed and the CVE is no longer reported.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies remediation. · Rule network-unauthenticated

CISA KEV Record

CISA KEV status was not determined for this record.

Change History & Source Data

— No recorded material change

CNA / source
openssl-security@openssl.org
Record status · verification
UPDATED · NVD API
CPE
cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*, cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*, cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*, cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*, cpe:2.3:a:netapp:cloud_volumes_ontap_mediator:-:*:*:*:*:*:*:*, cpe:2.3:a:netapp:clustered_data_ontap:-:*:*:*:*:*:*:*, cpe:2.3:a:netapp:clustered_data_ontap_antivirus_connector:-:*:*:*:*:*:*:*, cpe:2.3:a:netapp:santricity_smi-s_provider:-:*:*:*:*:*:*:*, cpe:2.3:a:netapp:storagegrid:-:*:*:*:*:*:*:*, cpe:2.3:o:netapp:a250_firmware:-:*:*:*:*:*:*:*

Evidence & Provenance

3 public sources
openssl.orgSource recordnvd.nist.govSource recordcert-portal.siemens.comSource record

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2022-0778
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2022-0778
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2022-0778"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.
Open KQL Library

Correlated briefings

— No published briefing references this CVE

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.