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

There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11

Unknown · libxml2

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

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 5 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 5 Oct 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 16.99% 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.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Unknown libxml2 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 5 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.

10 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 · communityqt5-qtwebengineVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.5.15.3_git20211112-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · mainlibxml2Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.2.9.11-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · communityqt5-qtwebengineVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.5.15.3_git20211112-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · mainlibxml2Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.2.9.11-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · communityqt5-qtwebengineVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.5.15.3_git20211112-r0Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · mainlibxml2Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.2.9.11-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcelibxml2Vendor fix publishedDebian records a fixed source-package version for this release.2.9.10+dfsg-6.6Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelibxml2Vendor fix publishedDebian records a fixed source-package version for this release.2.9.10+dfsg-6.6Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelibxml2Vendor fix publishedDebian records a fixed source-package version for this release.2.9.10+dfsg-6.6Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelibxml2Vendor fix publishedDebian records a fixed source-package version for this release.2.9.10+dfsg-6.6Debian Security Tracker ↗Source updated 5 Oct 2026
Open-source package ranges1 source-attributed range

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
RubyGemsnokogiriECOSYSTEM: introduced 0; fixed 1.11.41.11.4OSV record ↗aggregator derived · 8 Mar 2024
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
CVE-2021-3517 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitylibxml2: Heap-based buffer overflow in xmlEncodeEntitiesInternal() in entities.c
12 known affected

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

  • compat-expat1 as a component of Red Hat Enterprise Linux 6
  • compat-expat1.src as a component of Red Hat Enterprise Linux 6
  • libxml2 as a component of Red Hat Enterprise Linux 6
  • libxml2-devel as a component of Red Hat Enterprise Linux 6
  • libxml2-python as a component of Red Hat Enterprise Linux 6
  • libxml2-static as a component of Red Hat Enterprise Linux 6
  • libxml2.src as a component of Red Hat Enterprise Linux 6
  • libxml2 as a component of Red Hat Enterprise Linux 7
  • libxml2-devel as a component of Red Hat Enterprise Linux 7
  • libxml2-python as a component of Red Hat Enterprise Linux 7
  • libxml2-static as a component of Red Hat Enterprise Linux 7
  • libxml2.src as a component of Red Hat Enterprise Linux 7
Summary
There is a flaw in the xml entity encoding functionality of libxml2. An attacker who is able to supply a crafted file to be processed by an application linked with the affected functionality of libxml2 could trigger an out-of-bounds read. The most likely impact of this flaw is to application availability, with some potential impact to confidentiality and integrity if an attacker is able to use memory information to further exploit the application.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
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
There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11. An attacker who is able to supply a crafted file to be processed by an application linked with the affected functionality of libxml2 could trigger an out-of-bounds read. The most likely impact of this flaw is to application availability, with some potential impact to confidentiality and integrity if an attacker is able to use memory information to further exploit the application.
Remediation
Update to V3.1.5 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-4443

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; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 5 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

There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11. An attacker who is able to supply a crafted file to be processed by an application linked with the affected functionality of libxml2 could trigger an out-of-bounds read. The most likely impact of this flaw is to application availability, with some potential impact to confidentiality and integrity if an attacker is able to use memory information to further exploit the application.

What

There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11. An attacker who is able to supply a crafted file to be processed by an application linked with the affected functionality of libxml2 could trigger an out-of-bounds read. The most likely impact of this flaw is to application availability, with some potential impact to confidentiality and integrity if an attacker is able to use memory information to further exploit the application.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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

There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11. An attacker who is able to supply a crafted file to be processed by an application linked with the affected functionality of libxml2 could trigger an out-of-bounds read. The most likely impact of this flaw is to application availability, with some potential impact to confidentiality and integrity if an attacker is able to use memory information to further exploit the application.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Out-of-bounds Write → 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-787 ↗

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

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:L/A:H

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.ILowIntegrity impact: A successful attack can cause a limited loss.AHighAvailability impact: A successful attack can cause a major loss.
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-787
A

Official authority intelligence

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

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-0395Splunk Splunk Enterprise: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Splunk Splunk Enterprise ausnutzen, um vertrauliche Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand zu verursachen, Daten zu manipulieren und einen Cross-Site-Scripting-Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2022-0196Oracle Java SE: Mehrere Schwachstellen

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

Official advisory ↗
BSI · German · WID-SEC-2023-1152libxml2: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in libxml2 ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20210526Security Bulletin 26 May 2021

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

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

VERecord?id=CVE-2021-3177 Référence CVE CVE-2021-32292 https://www.cve.org/CVERecord?id=CVE-2021-32292 Référence CVE CVE-2021-3326 https://www.cve.org/CVERecord?id=CVE-2021-3326 Référence CVE CVE-2021-33294 https://www.cve.org/CVERecord?id=CVE-2021-33294 Référence CVE CVE-2021-33560 https://www.cve.org/CVERecord?id=CVE-2021-33560 Référence CVE CVE-2021-33574 https://www.cve.org/CVERecord?id=CVE-2021-33574 Référence CVE CVE-2021-33910 https://www.cve.org/CVERecord?id=CVE-2021-33910 Référence CVE CVE-2021-3426 https://www.cve.org/CVERecord?id=CVE-2021-3426 Référence CVE CVE-2021-3516 https://www.cve.org/CVERecord?id=CVE-2021-3516 Référence CVE CVE-2021-3517 https://www.cve.org/CVERecord?id=CVE-2021-3517 Référence CVE CVE-2021-3518 https://www.cve.org/CVERecord?id=CVE-2021-3518 Référence CVE CVE-2021-3520 https://www.cve.org/CVERecord?id=CVE-2021-3520 Référence CVE CVE-2021-3537 https://www.cve.org/CVERecord?id=CVE-2021-3537 Référence CVE CVE-2021-3541 https://www.cve.org/CVERecord?id=CVE-2021-3541 Référence CVE CVE-2021-3580 https://www.cve.org/CVERecord?id=CVE-2021-3580 Référence CVE CVE-2021-35942 https://www.cve.org/CVERecord?id=CVE-2021-35942 Référence CVE CVE-2021-36084 https://www.cve.org/CVERecord?id=CVE-2021-36084 Référence CVE CVE-2021-36085 https://www.cve.org/CVERecord?id=CVE-2021-36

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

ecord?id=CVE-2020-15358 Référence CVE CVE-2020-24977 https://www.cve.org/CVERecord?id=CVE-2020-24977 Référence CVE CVE-2020-35525 https://www.cve.org/CVERecord?id=CVE-2020-35525 Référence CVE CVE-2020-35527 https://www.cve.org/CVERecord?id=CVE-2020-35527 Référence CVE CVE-2020-7595 https://www.cve.org/CVERecord?id=CVE-2020-7595 Référence CVE CVE-2020-9327 https://www.cve.org/CVERecord?id=CVE-2020-9327 Référence CVE CVE-2021-20227 https://www.cve.org/CVERecord?id=CVE-2021-20227 Référence CVE CVE-2021-30560 https://www.cve.org/CVERecord?id=CVE-2021-30560 Référence CVE CVE-2021-31239 https://www.cve.org/CVERecord?id=CVE-2021-31239 Référence CVE CVE-2021-3517 https://www.cve.org/CVERecord?id=CVE-2021-3517 Référence CVE CVE-2021-3518 https://www.cve.org/CVERecord?id=CVE-2021-3518 Référence CVE CVE-2021-3537 https://www.cve.org/CVERecord?id=CVE-2021-3537 Référence CVE CVE-2021-3541 https://www.cve.org/CVERecord?id=CVE-2021-3541 Référence CVE CVE-2021-36690 https://www.cve.org/CVERecord?id=CVE-2021-36690 Référence CVE CVE-2021-3672 https://www.cve.org/CVERecord?id=CVE-2021-3672 Référence CVE CVE-2021-45346 https://www.cve.org/CVERecord?id=CVE-2021-45346 Référence CVE CVE-2022-22576 https://www.cve.org/CVERecord?id=CVE-2022-22576 Référence CVE CVE-2022-23308 https://www.cve.org/CVERecord?id=CVE-2022-

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

rier 2023 https://advisory.splunk.com/advisories/SVD-2023-0203 Bulletin de sécurité Splunk SVD-2023-0205 du 14 février 2023 https://advisory.splunk.com/advisories/SVD-2023-0205 Bulletin de sécurité Splunk SVD-2023-0210 du 14 février 2023 https://advisory.splunk.com/advisories/SVD-2023-0210 Bulletin de sécurité Splunk SVD-2023-0215 du 14 février 2023 https://advisory.splunk.com/advisories/SVD-2023-0215 Référence CVE CVE-2015-20107 https://www.cve.org/CVERecord?id=CVE-2015-20107 Référence CVE CVE-2021-21419 https://www.cve.org/CVERecord?id=CVE-2021-21419 Référence CVE CVE-2021-28957 https://www.cve.org/CVERecord?id=CVE-2021-28957 Référence CVE CVE-2021-3517 https://www.cve.org/CVERecord?id=CVE-2021-3517 Référence CVE CVE-2021-3518 https://www.cve.org/CVERecord?id=CVE-2021-3518 Référence CVE CVE-2021-3537 https://www.cve.org/CVERecord?id=CVE-2021-3537 Référence CVE CVE-2022-24785 https://www.cve.org/CVERecord?id=CVE-2022-24785 Référence CVE CVE-2022-31129 https://www.cve.org/CVERecord?id=CVE-2022-31129 Référence CVE CVE-2022-32212 https://www.cve.org/CVERecord?id=CVE-2022-32212 Référence CVE CVE-2023-22931 https://www.cve.org/CVERecord?id=CVE-2023-22931 Référence CVE CVE-2023-22932 https://www.cve.org/CVERecord?id=CVE-2023-22932 Référence CVE CVE-2023-22933 https://www.cve.org/CVERecord?id=CVE-2

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

ecord?id=CVE-2021-22946 Référence CVE CVE-2021-23017 https://www.cve.org/CVERecord?id=CVE-2021-23017 Référence CVE CVE-2021-23839 https://www.cve.org/CVERecord?id=CVE-2021-23839 Référence CVE CVE-2021-23840 https://www.cve.org/CVERecord?id=CVE-2021-23840 Référence CVE CVE-2021-23841 https://www.cve.org/CVERecord?id=CVE-2021-23841 Référence CVE CVE-2021-28950 https://www.cve.org/CVERecord?id=CVE-2021-28950 Référence CVE CVE-2021-3177 https://www.cve.org/CVERecord?id=CVE-2021-3177 Référence CVE CVE-2021-33574 https://www.cve.org/CVERecord?id=CVE-2021-33574 Référence CVE CVE-2021-3487 https://www.cve.org/CVERecord?id=CVE-2021-3487 Référence CVE CVE-2021-3517 https://www.cve.org/CVERecord?id=CVE-2021-3517 Référence CVE CVE-2021-3520 https://www.cve.org/CVERecord?id=CVE-2021-3520 Référence CVE CVE-2021-35550 https://www.cve.org/CVERecord?id=CVE-2021-35550 Référence CVE CVE-2021-35556 https://www.cve.org/CVERecord?id=CVE-2021-35556 Référence CVE CVE-2021-35559 https://www.cve.org/CVERecord?id=CVE-2021-35559 Référence CVE CVE-2021-35561 https://www.cve.org/CVERecord?id=CVE-2021-35561 Référence CVE CVE-2021-35564 https://www.cve.org/CVERecord?id=CVE-2021-35564 Référence CVE CVE-2021-35565 https://www.cve.org/CVERecord?id=CVE-2021-35565 Référence CVE CVE-2021-35567 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-351Multiples vulnérabilités dans les logiciels Juniper

Record?id=CVE-2019-1387 Référence CVE CVE-2020-35654 https://www.cve.org/CVERecord?id=CVE-2020-35654 Référence CVE CVE-2020-7774 https://www.cve.org/CVERecord?id=CVE-2020-7774 Référence CVE CVE-2021-23017 https://www.cve.org/CVERecord?id=CVE-2021-23017 Référence CVE CVE-2021-25289 https://www.cve.org/CVERecord?id=CVE-2021-25289 Référence CVE CVE-2021-26691 https://www.cve.org/CVERecord?id=CVE-2021-26691 Référence CVE CVE-2021-3156 https://www.cve.org/CVERecord?id=CVE-2021-3156 Référence CVE CVE-2021-31597 https://www.cve.org/CVERecord?id=CVE-2021-31597 Référence CVE CVE-2021-34552 https://www.cve.org/CVERecord?id=CVE-2021-34552 Référence CVE CVE-2021-3517 https://www.cve.org/CVERecord?id=CVE-2021-3517 Référence CVE CVE-2021-3560 https://www.cve.org/CVERecord?id=CVE-2021-3560 Référence CVE CVE-2021-4034 https://www.cve.org/CVERecord?id=CVE-2021-4034 Référence CVE CVE-2022-22187 https://www.cve.org/CVERecord?id=CVE-2022-22187 Référence CVE CVE-2022-22189 https://www.cve.org/CVERecord?id=CVE-2022-22189 Référence CVE CVE-2022-22190 https://www.cve.org/CVERecord?id=CVE-2022-22190 Gestion détaillée du document le 15 avril 2022 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr fr

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-054Multiples vulnérabilités dans Oracle Systems

De multiples vulnérabilités ont été découvertes dans Oracle Systems. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2021-AVI-803Multiples vulnérabilités dans Oracle Java SE

De multiples vulnérabilités ont été découvertes dans Oracle Java SE. Elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à l'intégrité des données et une atteinte à la confidentialité des données.

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

org/CVERecord?id=CVE-2021-29894 Référence CVE CVE-2021-30661 https://www.cve.org/CVERecord?id=CVE-2021-30661 Référence CVE CVE-2021-3177 https://www.cve.org/CVERecord?id=CVE-2021-3177 Référence CVE CVE-2021-3326 https://www.cve.org/CVERecord?id=CVE-2021-3326 Référence CVE CVE-2021-33910 https://www.cve.org/CVERecord?id=CVE-2021-33910 Référence CVE CVE-2021-3421 https://www.cve.org/CVERecord?id=CVE-2021-3421 Référence CVE CVE-2021-3449 https://www.cve.org/CVERecord?id=CVE-2021-3449 Référence CVE CVE-2021-3450 https://www.cve.org/CVERecord?id=CVE-2021-3450 Référence CVE CVE-2021-3516 https://www.cve.org/CVERecord?id=CVE-2021-3516 Référence CVE CVE-2021-3517 https://www.cve.org/CVERecord?id=CVE-2021-3517 Référence CVE CVE-2021-3518 https://www.cve.org/CVERecord?id=CVE-2021-3518 Référence CVE CVE-2021-3520 https://www.cve.org/CVERecord?id=CVE-2021-3520 Référence CVE CVE-2021-3537 https://www.cve.org/CVERecord?id=CVE-2021-3537 Référence CVE CVE-2021-3541 https://www.cve.org/CVERecord?id=CVE-2021-3541 Référence CVE CVE-2021-3609 https://www.cve.org/CVERecord?id=CVE-2021-3609 Gestion détaillée du document le 15 octobre 2021 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-031331Nokogiriにおけるバッファエラーの脆弱性

Nokogiri 1.11.4以前のバージョン（CRuby実装のみで、パッケージ化またはベンダー提供されたlibxml2を使用している場合）は、libxml2 2.9.10をバンドルしており、これはlibxml2 2.9.12で対処された複数の脆弱性の影響を受けます。これらの脆弱性には、xmlSchemaValidateStreamのメモリリーク（CVE-2019-20388）、xmlEncodeEntitiesInternalのグローバルバッファのオーバーリード（CVE-2020-24977）、ヒープベースのバッファオーバーフロー（CVE-2021-3517）、および境界外読み取り（CVE-2021-3518）が含まれます。細工されたXMLドキュメントを処理すると、サービス拒否、情報漏洩、またはメモリ破損を引き起こす可能性があります。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-003739libxml2 における境界外書き込みに関する脆弱性

libxml2 には、境界外書き込みに関する脆弱性が存在します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-003526Oracle Java SE および Oracle GraalVM Enterprise Edition における JSSE に関する脆弱性

Oracle Java SE および Oracle GraalVM Enterprise Edition には、JSSE に関する処理に不備があるため、機密性に影響のある脆弱性が存在します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-003517Oracle Java SE における Deployment に関する脆弱性

Oracle Java SE には、Deployment に関する処理に不備があるため、機密性、完全性、および可用性に影響のある脆弱性が存在します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-003599Oracle Java SE および Oracle GraalVM Enterprise Edition における JSSE に関する脆弱性

Oracle Java SE および Oracle GraalVM Enterprise Edition には、JSSE に関する処理に不備があるため、機密性に影響のある脆弱性が存在します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-003527Oracle Java SE および Oracle GraalVM Enterprise Edition における Swing に関する脆弱性

Oracle Java SE および Oracle GraalVM Enterprise Edition には、Swing に関する処理に不備があるため、可用性に影響のある脆弱性が存在します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-003524Oracle Java SE および Oracle GraalVM Enterprise Edition における Libraries に関する脆弱性

Oracle Java SE および Oracle GraalVM Enterprise Edition には、Libraries に関する処理に不備があるため、機密性に影響のある脆弱性が存在します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-003522Oracle Java SE および Oracle GraalVM Enterprise Edition における JSSE に関する脆弱性

Oracle Java SE および Oracle GraalVM Enterprise Edition には、JSSE に関する処理に不備があるため、可用性に影響のある脆弱性が存在します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-003521Oracle Java SE および Oracle GraalVM Enterprise Edition における Keytool に関する脆弱性

Oracle Java SE および Oracle GraalVM Enterprise Edition には、Keytool に関する処理に不備があるため、完全性に影響のある脆弱性が存在します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-003518Oracle Java SE および Oracle GraalVM Enterprise Edition における Utility に関する脆弱性

Oracle Java SE および Oracle GraalVM Enterprise Edition には、Utility に関する処理に不備があるため、可用性に影響のある脆弱性が存在します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-003516Oracle Java SE および Oracle GraalVM Enterprise Edition における Swing に関する脆弱性

Oracle Java SE および Oracle GraalVM Enterprise Edition には、Swing に関する処理に不備があるため、可用性に影響のある脆弱性が存在します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-003496Oracle Java SE および Oracle GraalVM Enterprise Edition における ImageIO に関する脆弱性

Oracle Java SE および Oracle GraalVM Enterprise Edition には、ImageIO に関する処理に不備があるため、可用性に影響のある脆弱性が存在します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-003475Oracle Java SE および Oracle GraalVM Enterprise Edition における JSSE に関する脆弱性

Oracle Java SE および Oracle GraalVM Enterprise Edition には、JSSE に関する処理に不備があるため、可用性に影響のある脆弱性が存在します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-003598Oracle Java SE および Oracle GraalVM Enterprise Edition における Hotspot に関する脆弱性

Oracle Java SE および Oracle GraalVM Enterprise Edition には、Hotspot に関する処理に不備があるため、可用性に影響のある脆弱性が存在します。

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 19 May 2021 · Last source change 2 Dec 2025, 21:34 UTC · CWE-787 · Out-of-bounds Write

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-4443
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
    libxml2 2.9.11 · 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
    libxml2 2.9.11 · 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
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2022-4443↗Vendor CSAF · Red Hat Product Security↗Siemens ProductCERT security advisory · Siemens SSA-398330↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
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-3517 · cve.blacktree.nl