BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2022
CVE-2022-43551High confidence

A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP

Unknown · https://github.com/curl/curl

Official source article: Siemens SSA-398330 ↗. Check the applicable product and release in the original source.

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 6 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 13 Feb 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 16.54% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown https://github.com/curl/curl and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 6 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · maincurlVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.87.0-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · maincurlVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.87.0-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · maincurlVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.7.87.0-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcecurlVendor fix publishedDebian records a fixed source-package version for this release.7.86.0-3Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcecurlVendor fix publishedDebian records a fixed source-package version for this release.7.86.0-3Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcecurlVendor fix publishedDebian records a fixed source-package version for this release.7.86.0-3Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcecurlVendor fix publishedDebian records a fixed source-package version for this release.7.86.0-3Debian Security Tracker ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

3 current
CVE-2022-43551 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitycurl: HSTS bypass via IDN
8 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • curl as a component of Red Hat Enterprise Linux 6
  • curl.src as a component of Red Hat Enterprise Linux 6
  • libcurl as a component of Red Hat Enterprise Linux 6
  • libcurl-devel as a component of Red Hat Enterprise Linux 6
  • curl as a component of Red Hat Enterprise Linux 7
  • curl.src as a component of Red Hat Enterprise Linux 7
  • libcurl as a component of Red Hat Enterprise Linux 7
  • libcurl-devel as a component of Red Hat Enterprise Linux 7
Summary
A vulnerability was found in curl. The issue can occur when curl's HSTS check is bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of an insecure clear-text HTTP step even when providing HTTP in the URL. Suppose the hostname in the given URL first uses IDN characters that get replaced with ASCII counterparts as part of the IDN conversion. In that case, it can bypass the HSTS mechanism using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E). Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the information, IDN encoded but looked for it as IDN decoded.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Applications using the APR libraries, such as httpd, must be restarted for this update to take effect. After installing the updated packages, the httpd daemon will be restarted automatically.
SSA-398330 · CSAF 2.0 · revision 18 · interimSiemens ProductCERTSSA-398330: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP >= V3.1.0 and < V3.1.5
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)
Summary
A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop U+002E (.). Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.
Remediation
Update to V3.1.5 or later version
SSA-892048 · CSAF 2.0 · revision 1 · finalSiemens ProductCERTSSA-892048: Third-Party Component Vulnerabilities in SINEC NMS before V1.0.3.1
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SINEC NMS
Summary
A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) `.`. Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.
Remediation
Update to V1.0.3.1 or later version
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-46548

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 6 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) `.`. Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.

What

A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) `.`. Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.

Why

The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) `.`. Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.

Why

The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Cleartext Transmission of Sensitive Information → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-319 ↗

CWE-319: Cleartext Transmission of Sensitive Information. The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-319Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2023-2229Splunk Splunk Enterprise: Mehrere Schwachstellen

Ein entfernter, authentifizierter Angreifer kann mehrere Schwachstellen in Splunk Splunk Enterprise ausnutzen, um beliebigen Code auszuführen, einen 'Denial of Service'-Zustand zu verursachen, seine Privilegien zu erweitern und weitere, nicht spezifizierte Auswirkungen zu verursachen.

Official advisory ↗
BSI · German · WID-SEC-2023-2031Xerox FreeFlow Print Server: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um die Vertraulichkeit, Verfügbarkeit und Integrität des Systems zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2023-1614Tenable Security Nessus Network Monitor: Mehrere Schwachstellen

Ein entfernter, anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in Tenable Security Nessus Network Monitor ausnutzen, um beliebigen Code auszuführen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand auszulösen und Daten zu manipulieren.

Official advisory ↗
BSI · German · WID-SEC-2023-1033Oracle MySQL: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle MySQL ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2023-1016Oracle Fusion Middleware: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Oracle Fusion Middleware ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2023-0777Apple macOS: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Apple macOS ausnutzen, um beliebigen Programmcode mit Administratorrechten auszuführen, beliebigen Programmcode auszuführen, Informationen offenzulegen, seine Privilegien zu erweitern, Dateien zu manipulieren, einen Denial of Service Zustand herbeizuführen, Sicherheitsvorkehrungen zu umgehen oder sonstige Auswirkungen zu verursachen.

Official advisory ↗
BSI · German · WID-SEC-2022-2375cURL: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen in cURL ausnutzen, um Sicherheitsvorkehrungen zu umgehen und einen Denial of Service Zustand herzustellen.

Official advisory ↗
BSI · German · WID-SEC-2024-3377Dell PowerProtect Data Domain: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen in Dell PowerProtect Data Domain ausnutzen, um seine Privilegien zu erhöhen, Informationen offenzulegen und um nicht näher beschriebene Auswirkungen zu erzielen.

Official advisory ↗
BSI · German · WID-SEC-2023-1350Splunk Splunk Enterprise: Mehrere Schwachstellen in Komponenten von Drittanbietern

Ein Angreifer kann mehrere Schwachstellen in Splunk Splunk Enterprise in diversen Komponenten von Drittanbietern ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20221228Security Bulletin 28 Dec 2022

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 28 Dec 2022, published on 28 December 2022. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0218Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2022-38476 Référence CVE CVE-2022-38533 https://www.cve.org/CVERecord?id=CVE-2022-38533 Référence CVE CVE-2022-3970 https://www.cve.org/CVERecord?id=CVE-2022-3970 Référence CVE CVE-2022-40090 https://www.cve.org/CVERecord?id=CVE-2022-40090 Référence CVE CVE-2022-40303 https://www.cve.org/CVERecord?id=CVE-2022-40303 Référence CVE CVE-2022-40304 https://www.cve.org/CVERecord?id=CVE-2022-40304 Référence CVE CVE-2022-40897 https://www.cve.org/CVERecord?id=CVE-2022-40897 Référence CVE CVE-2022-41409 https://www.cve.org/CVERecord?id=CVE-2022-41409 Référence CVE CVE-2022-4285 https://www.cve.org/CVERecord?id=CVE-2022-4285 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-44840 https://www.cve.org/CVERecord?id=CVE-2022-44840 Référence CVE CVE-2022-45703 https://www.cve.org/CVERecord?id=CVE-2022-45703 Référence CVE CVE-2022-4645 https://www.cve.org/CVERecord?id=CVE-2022-4645 Référence CVE CVE-2022-47007 https://www.cve.org/CVERecord?id=CVE-2022-47007 Référence CVE CVE-2022-47008 https://www.cve.org/CVERecord?id=CVE-2022-47008 Référence CVE CVE-2022-47010 https://www.cve.org/CVERecord?id=CVE-2022-47010 Référence CVE CVE-2022-47011 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0199Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2022-41724 Référence CVE CVE-2022-41725 https://www.cve.org/CVERecord?id=CVE-2022-41725 Référence CVE CVE-2022-41854 https://www.cve.org/CVERecord?id=CVE-2022-41854 Référence CVE CVE-2022-42003 https://www.cve.org/CVERecord?id=CVE-2022-42003 Référence CVE CVE-2022-42004 https://www.cve.org/CVERecord?id=CVE-2022-42004 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-42915 https://www.cve.org/CVERecord?id=CVE-2022-42915 Référence CVE CVE-2022-42916 https://www.cve.org/CVERecord?id=CVE-2022-42916 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-48174 https://www.cve.org/CVERecord?id=CVE-2022-48174 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-04

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

VERecord?id=CVE-2022-3903 Référence CVE CVE-2022-3996 https://www.cve.org/CVERecord?id=CVE-2022-3996 Référence CVE CVE-2022-40303 https://www.cve.org/CVERecord?id=CVE-2022-40303 Référence CVE CVE-2022-40304 https://www.cve.org/CVERecord?id=CVE-2022-40304 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-42898 https://www.cve.org/CVERecord?id=CVE-2022-42898 Référence CVE CVE-2022-42915 https://www.cve.org/CVERecord?id=CVE-2022-42915 Référence CVE CVE-2022-42916 https://www.cve.org/CVERecord?id=CVE-2022-42916 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-43680 https://www.cve.org/CVERecord?id=CVE-2022-43680 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-46908 https://www.cve.org/CVERecord?id=CVE-2022-46908 Référence CVE CVE-2022-48632 https://www.cve.org/CVERecord?id=CVE-2022-48632 Référence CVE CVE-2022-48637 https://www.cve.org/CVERecord?id=CVE-2022-48637 Référence CVE CVE-2022-48639 https://www.cve.org/CVERecord?id=CVE-2022-48639 Référence CVE CVE-2022-48640 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

d?id=CVE-2022-43242 Référence CVE CVE-2022-43243 https://www.cve.org/CVERecord?id=CVE-2022-43243 Référence CVE CVE-2022-43244 https://www.cve.org/CVERecord?id=CVE-2022-43244 Référence CVE CVE-2022-43245 https://www.cve.org/CVERecord?id=CVE-2022-43245 Référence CVE CVE-2022-43248 https://www.cve.org/CVERecord?id=CVE-2022-43248 Référence CVE CVE-2022-43249 https://www.cve.org/CVERecord?id=CVE-2022-43249 Référence CVE CVE-2022-43250 https://www.cve.org/CVERecord?id=CVE-2022-43250 Référence CVE CVE-2022-43252 https://www.cve.org/CVERecord?id=CVE-2022-43252 Référence CVE CVE-2022-43253 https://www.cve.org/CVERecord?id=CVE-2022-43253 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-43680 https://www.cve.org/CVERecord?id=CVE-2022-43680 Référence CVE CVE-2022-4415 https://www.cve.org/CVERecord?id=CVE-2022-4415 Référence CVE CVE-2022-44267 https://www.cve.org/CVERecord?id=CVE-2022-44267 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-44638 https://www.cve.org/CVERecord?id=CVE-2022-44638 Référence CVE CVE-2022-45061 https://www.cve.org/CVERecord?id=CVE-2022-45061 Référence CVE CVE-2022-45873 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0622Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2022-41720 Référence CVE CVE-2022-41722 https://www.cve.org/CVERecord?id=CVE-2022-41722 Référence CVE CVE-2022-41723 https://www.cve.org/CVERecord?id=CVE-2022-41723 Référence CVE CVE-2022-41724 https://www.cve.org/CVERecord?id=CVE-2022-41724 Référence CVE CVE-2022-41725 https://www.cve.org/CVERecord?id=CVE-2022-41725 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-42915 https://www.cve.org/CVERecord?id=CVE-2022-42915 Référence CVE CVE-2022-42916 https://www.cve.org/CVERecord?id=CVE-2022-42916 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-49636 https://www.cve.org/CVERecord?id=CVE-2022-49636 Référence CVE CVE-2022-49728 https://www.cve.org/CVERecord?id=CVE-2022-49728 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-1015Multiples vulnérabilités dans les produits Siemens

cord?id=CVE-2022-3821 Référence CVE CVE-2022-40303 https://www.cve.org/CVERecord?id=CVE-2022-40303 Référence CVE CVE-2022-40304 https://www.cve.org/CVERecord?id=CVE-2022-40304 Référence CVE CVE-2022-40674 https://www.cve.org/CVERecord?id=CVE-2022-40674 Référence CVE CVE-2022-42784 https://www.cve.org/CVERecord?id=CVE-2022-42784 Référence CVE CVE-2022-42898 https://www.cve.org/CVERecord?id=CVE-2022-42898 Référence CVE CVE-2022-42915 https://www.cve.org/CVERecord?id=CVE-2022-42915 Référence CVE CVE-2022-42916 https://www.cve.org/CVERecord?id=CVE-2022-42916 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-43680 https://www.cve.org/CVERecord?id=CVE-2022-43680 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-45061 https://www.cve.org/CVERecord?id=CVE-2022-45061 Référence CVE CVE-2022-45873 https://www.cve.org/CVERecord?id=CVE-2022-45873 Référence CVE CVE-2022-46141 https://www.cve.org/CVERecord?id=CVE-2022-46141 Référence CVE CVE-2022-46143 https://www.cve.org/CVERecord?id=CVE-2022-46143 Référence CVE CVE-2022-46908 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0701Multiples vulnérabilités dans Splunk

d?id=CVE-2022-40899 Référence CVE CVE-2022-41715 https://www.cve.org/CVERecord?id=CVE-2022-41715 Référence CVE CVE-2022-41716 https://www.cve.org/CVERecord?id=CVE-2022-41716 Référence CVE CVE-2022-41720 https://www.cve.org/CVERecord?id=CVE-2022-41720 Référence CVE CVE-2022-41722 https://www.cve.org/CVERecord?id=CVE-2022-41722 Référence CVE CVE-2022-42003 https://www.cve.org/CVERecord?id=CVE-2022-42003 Référence CVE CVE-2022-42004 https://www.cve.org/CVERecord?id=CVE-2022-42004 Référence CVE CVE-2022-42915 https://www.cve.org/CVERecord?id=CVE-2022-42915 Référence CVE CVE-2022-42916 https://www.cve.org/CVERecord?id=CVE-2022-42916 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-46175 https://www.cve.org/CVERecord?id=CVE-2022-46175 Référence CVE CVE-2023-23914 https://www.cve.org/CVERecord?id=CVE-2023-23914 Référence CVE CVE-2023-23915 https://www.cve.org/CVERecord?id=CVE-2023-23915 Référence CVE CVE-2023-23916 https://www.cve.org/CVERecord?id=CVE-2023-23916 Référence CVE CVE-2023-24539 https://www.cve.org/CVERecord?id=CVE-2023-24539 Référence CVE CVE-2023-24540 https://www.cve.org/CVERecord?id=CVE-2023-24540 Référence CVE CVE-2023-27533 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0627Multiples vulnérabilités dans IBM Spectrum

org/CVERecord?id=CVE-2022-35252 Référence CVE CVE-2022-3566 https://www.cve.org/CVERecord?id=CVE-2022-3566 Référence CVE CVE-2022-3567 https://www.cve.org/CVERecord?id=CVE-2022-3567 Référence CVE CVE-2022-3623 https://www.cve.org/CVERecord?id=CVE-2022-3623 Référence CVE CVE-2022-3625 https://www.cve.org/CVERecord?id=CVE-2022-3625 Référence CVE CVE-2022-3628 https://www.cve.org/CVERecord?id=CVE-2022-3628 Référence CVE CVE-2022-4129 https://www.cve.org/CVERecord?id=CVE-2022-4129 Référence CVE CVE-2022-42703 https://www.cve.org/CVERecord?id=CVE-2022-42703 Référence CVE CVE-2022-42721 https://www.cve.org/CVERecord?id=CVE-2022-42721 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2023-0394 https://www.cve.org/CVERecord?id=CVE-2023-0394 Référence CVE CVE-2023-0461 https://www.cve.org/CVERecord?id=CVE-2023-0461 Référence CVE CVE-2023-1195 https://www.cve.org/CVERecord?id=CVE-2023-1195 Référence CVE CVE-2023-23934 https://www.cve.org/CVERecord?id=CVE-2023-23934 Référence CVE CVE-2023-24329 https://www.cve.org/CVERecord?id=CVE-2023-24329 Référence CVE CVE-2023-2454 https://www.cve.org/CVERecord?id=CVE-2023-2454 Référence CVE CVE-2023-2455 https://www.cve.org/CVERecord?id=CVE-2023-

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0499Multiples vulnérabilités dans Tenable Nessus Network Monitor

d?id=CVE-2022-32207 Référence CVE CVE-2022-32208 https://www.cve.org/CVERecord?id=CVE-2022-32208 Référence CVE CVE-2022-32221 https://www.cve.org/CVERecord?id=CVE-2022-32221 Référence CVE CVE-2022-35252 https://www.cve.org/CVERecord?id=CVE-2022-35252 Référence CVE CVE-2022-35737 https://www.cve.org/CVERecord?id=CVE-2022-35737 Référence CVE CVE-2022-40303 https://www.cve.org/CVERecord?id=CVE-2022-40303 Référence CVE CVE-2022-40304 https://www.cve.org/CVERecord?id=CVE-2022-40304 Référence CVE CVE-2022-42915 https://www.cve.org/CVERecord?id=CVE-2022-42915 Référence CVE CVE-2022-42916 https://www.cve.org/CVERecord?id=CVE-2022-42916 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-46908 https://www.cve.org/CVERecord?id=CVE-2022-46908 Référence CVE CVE-2022-4904 https://www.cve.org/CVERecord?id=CVE-2022-4904 Référence CVE CVE-2023-0465 https://www.cve.org/CVERecord?id=CVE-2023-0465 Référence CVE CVE-2023-0466 https://www.cve.org/CVERecord?id=CVE-2023-0466 Référence CVE CVE-2023-1255 https://www.cve.org/CVERecord?id=CVE-2023-1255 Référence CVE CVE-2023-23914 https://www.cve.org/CVERecord?id=CVE-2023-23914 Référence CVE CVE-2023-23915 https://www.cve.org/CVERecord?id=CVE-2023

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0484Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2022-41717 Référence CVE CVE-2022-41721 https://www.cve.org/CVERecord?id=CVE-2022-41721 Référence CVE CVE-2022-41722 https://www.cve.org/CVERecord?id=CVE-2022-41722 Référence CVE CVE-2022-41723 https://www.cve.org/CVERecord?id=CVE-2022-41723 Référence CVE CVE-2022-41724 https://www.cve.org/CVERecord?id=CVE-2022-41724 Référence CVE CVE-2022-41725 https://www.cve.org/CVERecord?id=CVE-2022-41725 Référence CVE CVE-2022-41727 https://www.cve.org/CVERecord?id=CVE-2022-41727 Référence CVE CVE-2022-4269 https://www.cve.org/CVERecord?id=CVE-2022-4269 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-4378 https://www.cve.org/CVERecord?id=CVE-2022-4378 Référence CVE CVE-2022-43927 https://www.cve.org/CVERecord?id=CVE-2022-43927 Référence CVE CVE-2022-43929 https://www.cve.org/CVERecord?id=CVE-2022-43929 Référence CVE CVE-2022-43930 https://www.cve.org/CVERecord?id=CVE-2022-43930 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2022-45061 https://www.cve.org/CVERecord?id=CVE-2022-45061 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0428Multiples vulnérabilités dans les produits Splunk

ecord?id=CVE-2022-40304 Référence CVE CVE-2022-41715 https://www.cve.org/CVERecord?id=CVE-2022-41715 Référence CVE CVE-2022-41716 https://www.cve.org/CVERecord?id=CVE-2022-41716 Référence CVE CVE-2022-41720 https://www.cve.org/CVERecord?id=CVE-2022-41720 Référence CVE CVE-2022-4200 https://www.cve.org/CVERecord?id=CVE-2022-4200 Référence CVE CVE-2022-42004 https://www.cve.org/CVERecord?id=CVE-2022-42004 Référence CVE CVE-2022-42915 https://www.cve.org/CVERecord?id=CVE-2022-42915 Référence CVE CVE-2022-42916 https://www.cve.org/CVERecord?id=CVE-2022-42916 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-43680 https://www.cve.org/CVERecord?id=CVE-2022-43680 Référence CVE CVE-2022-46175 https://www.cve.org/CVERecord?id=CVE-2022-46175 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-1370 https://www.cve.org/CVERecord?id=CVE-2023-1370 Référence CVE CVE-2023-23914 https://www.cve.org/CVERecord?id=CVE-2023-23914 Référence CVE CVE-2023-23915 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0385Multiples vulnérabilités dans les produits VMware Tanzu

De multiples vulnérabilités ont été découvertes dans VMware Tanzu . Elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données, un déni de service à distance et une exécution de code arbitraire à distance.

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0370Multiples vulnérabilités dans les produits Siemens

emens SSA-932528 du 09 mai 2023 https://cert-portal.siemens.com/productcert/html/ssa-892048.html Référence CVE CVE-2019-10936 https://www.cve.org/CVERecord?id=CVE-2019-10936 Référence CVE CVE-2022-32221 https://www.cve.org/CVERecord?id=CVE-2022-32221 Référence CVE CVE-2022-35252 https://www.cve.org/CVERecord?id=CVE-2022-35252 Référence CVE CVE-2022-35260 https://www.cve.org/CVERecord?id=CVE-2022-35260 Référence CVE CVE-2022-40674 https://www.cve.org/CVERecord?id=CVE-2022-40674 Référence CVE CVE-2022-42915 https://www.cve.org/CVERecord?id=CVE-2022-42915 Référence CVE CVE-2022-42916 https://www.cve.org/CVERecord?id=CVE-2022-42916 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-43680 https://www.cve.org/CVERecord?id=CVE-2022-43680 Référence CVE CVE-2022-47522 https://www.cve.org/CVERecord?id=CVE-2022-47522 Référence CVE CVE-2023-0973 https://www.cve.org/CVERecord?id=CVE-2023-0973 Référence CVE CVE-2023-27407 https://www.cve.org/CVERecord?id=CVE-2023-27407 Référence CVE CVE-2023-27408 https://www.cve.org/CVERecord?id=CVE-2023-27408 Référence CVE CVE-2023-27409 https://www.cve.org/CVERecord?id=CVE-2023-27409 Référence CVE CVE-2023-27410 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0325Multiples vulnérabilités dans les produits Oracle

rd?id=CVE-2022-1471 Référence CVE CVE-2022-31160 https://www.cve.org/CVERecord?id=CVE-2022-31160 Référence CVE CVE-2022-34169 https://www.cve.org/CVERecord?id=CVE-2022-34169 Référence CVE CVE-2022-36033 https://www.cve.org/CVERecord?id=CVE-2022-36033 Référence CVE CVE-2022-37434 https://www.cve.org/CVERecord?id=CVE-2022-37434 Référence CVE CVE-2022-40152 https://www.cve.org/CVERecord?id=CVE-2022-40152 Référence CVE CVE-2022-41881 https://www.cve.org/CVERecord?id=CVE-2022-41881 Référence CVE CVE-2022-42916 https://www.cve.org/CVERecord?id=CVE-2022-42916 Référence CVE CVE-2022-43548 https://www.cve.org/CVERecord?id=CVE-2022-43548 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-45047 https://www.cve.org/CVERecord?id=CVE-2022-45047 Référence CVE CVE-2022-45061 https://www.cve.org/CVERecord?id=CVE-2022-45061 Référence CVE CVE-2022-45143 https://www.cve.org/CVERecord?id=CVE-2022-45143 Référence CVE CVE-2022-45685 https://www.cve.org/CVERecord?id=CVE-2022-45685 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-21896 https://www.cve.org/CVERecord?id=CVE-2023-21896 Référence CVE CVE-2023-21911 https://www.cve.org/CVERecord?id=CVE-2023-21911 Référence CVE CVE-2023-21912 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0265Multiples vulnérabilités dans les produits Apple

Bulletin de sécurité Apple HT213673 du 27 mars 2023 https://support.apple.com/en-us/HT213673 Bulletin de sécurité Apple HT213674 du 27 mars 2023 https://support.apple.com/en-us/HT213674 Bulletin de sécurité Apple HT213675 du 27 mars 2023 https://support.apple.com/en-us/HT213675 Bulletin de sécurité Apple HT213676 du 27 mars 2023 https://support.apple.com/en-us/HT213676 Bulletin de sécurité Apple HT213677 du 27 mars 2023 https://support.apple.com/en-us/HT213677 Bulletin de sécurité Apple HT213678 du 27 mars 2023 https://support.apple.com/en-us/HT213678 Référence CVE CVE-2022-26702 https://www.cve.org/CVERecord?id=CVE-2022-26702 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2023-0049 https://www.cve.org/CVERecord?id=CVE-2023-0049 Référence CVE CVE-2023-0051 https://www.cve.org/CVERecord?id=CVE-2023-0051 Référence CVE CVE-2023-0054 https://www.cve.org/CVERecord?id=CVE-2023-0054 Référence CVE CVE-2023-0288 https://www.cve.org/CVERecord?id=CVE-2023-0288 Référence CVE CVE-2023-0433 https://www.cve.org/CVERecord?id=CVE-2023-0433 Référence CVE CVE-2023-0512 https://www.cve.org/CVERecord?id=CVE-2023-0512 Référence CVE CVE-2023-23494 https://www.cve.org/CVERecord?id=CVE-2023-234

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0258Multiples vulnérabilités dans les produits IBM

/CVERecord?id=CVE-2022-3996 Référence CVE CVE-2022-4139 https://www.cve.org/CVERecord?id=CVE-2022-4139 Référence CVE CVE-2022-41715 https://www.cve.org/CVERecord?id=CVE-2022-41715 Référence CVE CVE-2022-41716 https://www.cve.org/CVERecord?id=CVE-2022-41716 Référence CVE CVE-2022-41717 https://www.cve.org/CVERecord?id=CVE-2022-41717 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Référence CVE CVE-2022-4269 https://www.cve.org/CVERecord?id=CVE-2022-4269 Référence CVE CVE-2022-4304 https://www.cve.org/CVERecord?id=CVE-2022-4304 Référence CVE CVE-2022-43548 https://www.cve.org/CVERecord?id=CVE-2022-43548 Référence CVE CVE-2022-43551 https://www.cve.org/CVERecord?id=CVE-2022-43551 Référence CVE CVE-2022-43552 https://www.cve.org/CVERecord?id=CVE-2022-43552 Référence CVE CVE-2022-43945 https://www.cve.org/CVERecord?id=CVE-2022-43945 Référence CVE CVE-2022-4450 https://www.cve.org/CVERecord?id=CVE-2022-4450 Référence CVE CVE-2023-0215 https://www.cve.org/CVERecord?id=CVE-2023-0215 Référence CVE CVE-2023-0216 https://www.cve.org/CVERecord?id=CVE-2023-0216 Référence CVE CVE-2023-0217 https://www.cve.org/CVERecord?id=CVE-2023-0217 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-0401 https://www.cve.org/CVERecord?id=CVE-2023-04

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0060Multiples vulnérabilités dans IBM QRadar WinCollect Agent

De multiples vulnérabilités ont été découvertes dans IBM QRadar WinCollect Agent. Elles permettent à un attaquant de provoquer un déni de service à distance et un contournement de la politique de sécurité.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-003876curl における重要な情報の平文での送信に関する脆弱性

curl には、重要な情報の平文での送信に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 23 Dec 2022 · Last source change 13 Feb 2026, 19:43 UTC · CWE-319 · Cleartext Transmission of Sensitive Information

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-46548
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    Fixed in curl 7.87.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    Fixed in curl 7.87.0 · Fixed: Update to V3.1.5 or later version
    Siemens ProductCERT ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Siemens ProductCERT ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-43551 · cve.blacktree.nl