BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2021
CVE-2021-22897High confidence

n/a https://github.com/curl/curl — security vulnerability

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

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

5.3MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium 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 severityMediumOperational priority:High, raised one band.upgradedsince 28 May 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 2.98% 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 30 daysRemediation target: Within 180 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.0Alpine 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.0Alpine 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.0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcecurlNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcecurlNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcecurlNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcecurlNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian 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.

2 current
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
curl 7.61.0 through 7.76.1 suffers from exposure of data element to wrong session due to a mistake in the code for CURLOPT_SSL_CIPHER_LIST when libcurl is built to use the Schannel TLS library. The selected cipher set was stored in a single "static" variable in the library, which has the surprising side-effect that if an application sets up multiple concurrent transfers, the last one that sets the ciphers will accidentally control the set used by all transfers. In a worst-case scenario, this weakens transport security significantly.
Remediation
Update to V3.1.5 or later version
SSA-389290 · CSAF 2.0 · revision 1 · finalSiemens ProductCERTSSA-389290: Third-Party Component Vulnerabilities in SINEC INS
1 known affected

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

  • SINEC INS
Summary
curl 7.61.0 through 7.76.1 suffers from exposure of data element to wrong session due to a mistake in the code for CURLOPT_SSL_CIPHER_LIST when libcurl is built to use the Schannel TLS library. The selected cipher set was stored in a single "static" variable in the library, which has the surprising side-effect that if an application sets up multiple concurrent transfers, the last one that sets the ciphers will accidentally control the set used by all transfers. In a worst-case scenario, this weakens transport security significantly.
Remediation
Update to V1.0.1.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-2021-10029

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

Medium 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

curl 7.61.0 through 7.76.1 suffers from exposure of data element to wrong session due to a mistake in the code for CURLOPT_SSL_CIPHER_LIST when libcurl is built to use the Schannel TLS library. The selected cipher set was stored in a single "static" variable in the library, which has the surprising side-effect that if an application sets up multiple concurrent transfers, the last one that sets the ciphers will accidentally control the set used by all transfers. In a worst-case scenario, this weakens transport security significantly.

What

curl 7.61.0 through 7.76.1 suffers from exposure of data element to wrong session due to a mistake in the code for CURLOPT_SSL_CIPHER_LIST when libcurl is built to use the Schannel TLS library. The selected cipher set was stored in a single "static" variable in the library, which has the surprising side-effect that if an application sets up multiple concurrent transfers, the last one that sets the ciphers will accidentally control the set used by all transfers. In a worst-case scenario, this weakens transport security significantly.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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

curl 7.61.0 through 7.76.1 suffers from exposure of data element to wrong session due to a mistake in the code for CURLOPT_SSL_CIPHER_LIST when libcurl is built to use the Schannel TLS library. The selected cipher set was stored in a single "static" variable in the library, which has the surprising side-effect that if an application sets up multiple concurrent transfers, the last one that sets the ciphers will accidentally control the set used by all transfers. In a worst-case scenario, this weakens transport security significantly.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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 → vulnerable operation → 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-840 ↗

CWE-840. Open the MITRE definition for the exact weakness description.

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:L/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.CLowConfidentiality impact: A successful attack can cause a limited 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-840Public 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-2025-2364Oracle JD Edwards: Mehrere Schwachstellen

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

Official advisory ↗
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-2022-0873cURL und libcurl: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen in cURL und libcurl ausnutzen, um Informationen offenzulegen oder beliebigen Programmcode auszuführen.

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-20210616Security Bulletin 16 Jun 2021

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 16 Jun 2021, published on 16 June 2021. 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

ord?id=CVE-2020-19726 Référence CVE CVE-2020-22916 https://www.cve.org/CVERecord?id=CVE-2020-22916 Référence CVE CVE-2020-27618 https://www.cve.org/CVERecord?id=CVE-2020-27618 Référence CVE CVE-2020-29562 https://www.cve.org/CVERecord?id=CVE-2020-29562 Référence CVE CVE-2020-2981 https://www.cve.org/CVERecord?id=CVE-2020-2981 Référence CVE CVE-2021-20197 https://www.cve.org/CVERecord?id=CVE-2021-20197 Référence CVE CVE-2021-20205 https://www.cve.org/CVERecord?id=CVE-2021-20205 Référence CVE CVE-2021-20266 https://www.cve.org/CVERecord?id=CVE-2021-20266 Référence CVE CVE-2021-20284 https://www.cve.org/CVERecord?id=CVE-2021-20284 Référence CVE CVE-2021-22897 https://www.cve.org/CVERecord?id=CVE-2021-22897 Référence CVE CVE-2021-22898 https://www.cve.org/CVERecord?id=CVE-2021-22898 Référence CVE CVE-2021-22901 https://www.cve.org/CVERecord?id=CVE-2021-22901 Référence CVE CVE-2021-22922 https://www.cve.org/CVERecord?id=CVE-2021-22922 Référence CVE CVE-2021-22923 https://www.cve.org/CVERecord?id=CVE-2021-22923 Référence CVE CVE-2021-22924 https://www.cve.org/CVERecord?id=CVE-2021-22924 Référence CVE CVE-2021-22925 https://www.cve.org/CVERecord?id=CVE-2021-22925 Référence CVE CVE-2021-22926 https://www.cve.org/CVERecord?id=CVE-2021-22926 Référence CVE CVE-2021-22945 https://www.cve.org/CVERecord?id=

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

ve.org/CVERecord?id=CVE-2019-5482 Référence CVE CVE-2019-5747 https://www.cve.org/CVERecord?id=CVE-2019-5747 Référence CVE CVE-2020-10750 https://www.cve.org/CVERecord?id=CVE-2020-10750 Référence CVE CVE-2020-1967 https://www.cve.org/CVERecord?id=CVE-2020-1967 Référence CVE CVE-2020-1971 https://www.cve.org/CVERecord?id=CVE-2020-1971 Référence CVE CVE-2020-8169 https://www.cve.org/CVERecord?id=CVE-2020-8169 Référence CVE CVE-2020-8177 https://www.cve.org/CVERecord?id=CVE-2020-8177 Référence CVE CVE-2020-8284 https://www.cve.org/CVERecord?id=CVE-2020-8284 Référence CVE CVE-2020-8908 https://www.cve.org/CVERecord?id=CVE-2020-8908 Référence CVE CVE-2021-22897 https://www.cve.org/CVERecord?id=CVE-2021-22897 Référence CVE CVE-2021-22898 https://www.cve.org/CVERecord?id=CVE-2021-22898 Référence CVE CVE-2021-22922 https://www.cve.org/CVERecord?id=CVE-2021-22922 Référence CVE CVE-2021-22923 https://www.cve.org/CVERecord?id=CVE-2021-22923 Référence CVE CVE-2021-22925 https://www.cve.org/CVERecord?id=CVE-2021-22925 Référence CVE CVE-2021-22926 https://www.cve.org/CVERecord?id=CVE-2021-22926 Référence CVE CVE-2021-22946 https://www.cve.org/CVERecord?id=CVE-2021-22946 Référence CVE CVE-2021-22947 https://www.cve.org/CVERecord?id=CVE-2021-22947 Référence CVE CVE-2021-23840 https://www.cve.org/CVERecord?id=

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

cord?id=CVE-2020-8492 Référence CVE CVE-2020-9327 https://www.cve.org/CVERecord?id=CVE-2020-9327 Référence CVE CVE-2021-20193 https://www.cve.org/CVERecord?id=CVE-2021-20193 Référence CVE CVE-2021-20227 https://www.cve.org/CVERecord?id=CVE-2021-20227 Référence CVE CVE-2021-20231 https://www.cve.org/CVERecord?id=CVE-2021-20231 Référence CVE CVE-2021-20232 https://www.cve.org/CVERecord?id=CVE-2021-20232 Référence CVE CVE-2021-20305 https://www.cve.org/CVERecord?id=CVE-2021-20305 Référence CVE CVE-2021-22876 https://www.cve.org/CVERecord?id=CVE-2021-22876 Référence CVE CVE-2021-22890 https://www.cve.org/CVERecord?id=CVE-2021-22890 Référence CVE CVE-2021-22897 https://www.cve.org/CVERecord?id=CVE-2021-22897 Référence CVE CVE-2021-22898 https://www.cve.org/CVERecord?id=CVE-2021-22898 Référence CVE CVE-2021-22901 https://www.cve.org/CVERecord?id=CVE-2021-22901 Référence CVE CVE-2021-22922 https://www.cve.org/CVERecord?id=CVE-2021-22922 Référence CVE CVE-2021-22923 https://www.cve.org/CVERecord?id=CVE-2021-22923 Référence CVE CVE-2021-22924 https://www.cve.org/CVERecord?id=CVE-2021-22924 Référence CVE CVE-2021-22925 https://www.cve.org/CVERecord?id=CVE-2021-22925 Référence CVE CVE-2021-22926 https://www.cve.org/CVERecord?id=CVE-2021-22926 Référence CVE CVE-2021-22945 https://www.cve.org/CVERecord?id=

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

/CVERecord?id=CVE-2020-8231 Référence CVE CVE-2020-8284 https://www.cve.org/CVERecord?id=CVE-2020-8284 Référence CVE CVE-2020-8285 https://www.cve.org/CVERecord?id=CVE-2020-8285 Référence CVE CVE-2020-8286 https://www.cve.org/CVERecord?id=CVE-2020-8286 Référence CVE CVE-2020-8908 https://www.cve.org/CVERecord?id=CVE-2020-8908 Référence CVE CVE-2021-20066 https://www.cve.org/CVERecord?id=CVE-2021-20066 Référence CVE CVE-2021-22569 https://www.cve.org/CVERecord?id=CVE-2021-22569 Référence CVE CVE-2021-22876 https://www.cve.org/CVERecord?id=CVE-2021-22876 Référence CVE CVE-2021-22890 https://www.cve.org/CVERecord?id=CVE-2021-22890 Référence CVE CVE-2021-22897 https://www.cve.org/CVERecord?id=CVE-2021-22897 Référence CVE CVE-2021-22898 https://www.cve.org/CVERecord?id=CVE-2021-22898 Référence CVE CVE-2021-22901 https://www.cve.org/CVERecord?id=CVE-2021-22901 Référence CVE CVE-2021-22922 https://www.cve.org/CVERecord?id=CVE-2021-22922 Référence CVE CVE-2021-22923 https://www.cve.org/CVERecord?id=CVE-2021-22923 Référence CVE CVE-2021-22924 https://www.cve.org/CVERecord?id=CVE-2021-22924 Référence CVE CVE-2021-22925 https://www.cve.org/CVERecord?id=CVE-2021-22925 Référence CVE CVE-2021-22926 https://www.cve.org/CVERecord?id=CVE-2021-22926 Référence CVE CVE-2021-22945 https://www.cve.org/CVERecord?id=

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

rg/CVERecord?id=CVE-2020-8177 Référence CVE CVE-2020-8203 https://www.cve.org/CVERecord?id=CVE-2020-8203 Référence CVE CVE-2020-8231 https://www.cve.org/CVERecord?id=CVE-2020-8231 Référence CVE CVE-2020-8284 https://www.cve.org/CVERecord?id=CVE-2020-8284 Référence CVE CVE-2020-8285 https://www.cve.org/CVERecord?id=CVE-2020-8285 Référence CVE CVE-2020-8286 https://www.cve.org/CVERecord?id=CVE-2020-8286 Référence CVE CVE-2021-20095 https://www.cve.org/CVERecord?id=CVE-2021-20095 Référence CVE CVE-2021-22876 https://www.cve.org/CVERecord?id=CVE-2021-22876 Référence CVE CVE-2021-22890 https://www.cve.org/CVERecord?id=CVE-2021-22890 Référence CVE CVE-2021-22897 https://www.cve.org/CVERecord?id=CVE-2021-22897 Référence CVE CVE-2021-22898 https://www.cve.org/CVERecord?id=CVE-2021-22898 Référence CVE CVE-2021-22901 https://www.cve.org/CVERecord?id=CVE-2021-22901 Référence CVE CVE-2021-22922 https://www.cve.org/CVERecord?id=CVE-2021-22922 Référence CVE CVE-2021-22923 https://www.cve.org/CVERecord?id=CVE-2021-22923 Référence CVE CVE-2021-22924 https://www.cve.org/CVERecord?id=CVE-2021-22924 Référence CVE CVE-2021-22925 https://www.cve.org/CVERecord?id=CVE-2021-22925 Référence CVE CVE-2021-22926 https://www.cve.org/CVERecord?id=CVE-2021-22926 Référence CVE CVE-2021-22945 https://www.cve.org/CVERecord?id=

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

/CVERecord?id=CVE-2020-8285 Référence CVE CVE-2020-8286 https://www.cve.org/CVERecord?id=CVE-2020-8286 Référence CVE CVE-2020-8287 https://www.cve.org/CVERecord?id=CVE-2020-8287 Référence CVE CVE-2020-8625 https://www.cve.org/CVERecord?id=CVE-2020-8625 Référence CVE CVE-2020-9327 https://www.cve.org/CVERecord?id=CVE-2020-9327 Référence CVE CVE-2021-22876 https://www.cve.org/CVERecord?id=CVE-2021-22876 Référence CVE CVE-2021-22883 https://www.cve.org/CVERecord?id=CVE-2021-22883 Référence CVE CVE-2021-22884 https://www.cve.org/CVERecord?id=CVE-2021-22884 Référence CVE CVE-2021-22890 https://www.cve.org/CVERecord?id=CVE-2021-22890 Référence CVE CVE-2021-22897 https://www.cve.org/CVERecord?id=CVE-2021-22897 Référence CVE CVE-2021-22898 https://www.cve.org/CVERecord?id=CVE-2021-22898 Référence CVE CVE-2021-22901 https://www.cve.org/CVERecord?id=CVE-2021-22901 Référence CVE CVE-2021-22918 https://www.cve.org/CVERecord?id=CVE-2021-22918 Référence CVE CVE-2021-22921 https://www.cve.org/CVERecord?id=CVE-2021-22921 Référence CVE CVE-2021-22922 https://www.cve.org/CVERecord?id=CVE-2021-22922 Référence CVE CVE-2021-22923 https://www.cve.org/CVERecord?id=CVE-2021-22923 Référence CVE CVE-2021-22924 https://www.cve.org/CVERecord?id=CVE-2021-22924 Référence CVE CVE-2021-22925 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-008166curl における誤った領域へのリソースの漏えいに関する脆弱性

curl には、誤った領域へのリソースの漏えいに関する脆弱性が存在します。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2025-0338Kwetsbaarheden verholpen in Oracle JD Edwards EnterpriseOne Tools

Multiple vulnerabilities in libcurl and TensorFlow dependencies expose sensitive data and require updates to address security issues across various versions.

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
Update to V3.1.5 or later version
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 11 Jun 2021 · Last source change 28 May 2026, 19:47 UTC · CWE-840

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-2021-10029
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
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
    7.61.0 through 7.76.1 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    7.61.0 through 7.76.1 · Fixed: Update to V3.1.5 or later version
    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-2021-22897 · cve.blacktree.nl