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

An incomplete string comparison in the numpy.core component in NumPy before 1.22.0 allows attackers to trigger slightly incorrect copying by constructing specific string objects

Unknown · Unknown

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 4 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 4 Aug 2024

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 1.56% 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 Unknown 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 4 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

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

4 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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
Debian trixietrixie · sourcenumpyAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcenumpyAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcenumpyAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcenumpyAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
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-0151

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 4 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

An incomplete string comparison in the numpy.core component in NumPy before 1.22.0 allows attackers to trigger slightly incorrect copying by constructing specific string objects. NOTE: the vendor states that this reported code behavior is "completely harmless."

What

An incomplete string comparison in the numpy.core component in NumPy before 1.22.0 allows attackers to trigger slightly incorrect copying by constructing specific string objects. NOTE: the vendor states that this reported code behavior is "completely harmless."

Why

The product compares two entities in a security-relevant context, but the comparison is incorrect.

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

An incomplete string comparison in the numpy.core component in NumPy before 1.22.0 allows attackers to trigger slightly incorrect copying by constructing specific string objects. NOTE: the vendor states that this reported code behavior is "completely harmless."

Why

The product compares two entities in a security-relevant context, but the comparison is incorrect.

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 → Incorrect Comparison → 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-697 ↗

CWE-697: Incorrect Comparison. The product compares two entities in a security-relevant context, but the comparison is incorrect.

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

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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.ALowAvailability impact: A successful attack can cause a limited 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-697Public 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-2022-0456tribe29 checkmk: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

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

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

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

Official advisory ↗
BSI · German · WID-SEC-2022-0302Xerox FreeFlow Print Server: Mehrere Schwachstellen ermöglichen Ausführen von beliebigem Programmcode mit Administratorrechten

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um beliebigen Programmcode auszuführen, einen Cross-Site-Scripting-Angriff durchzuführen, Informationen offenzulegen, einen Denial-of-Service-Zustand zu verursachen oder Dateien zu manipulieren.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20211222Security Bulletin 22 Dec 2021

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

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0585Multiples vulnérabilités dans VMware Tanzu

.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/35935 Référence CVE CVE-2015-1197 https://www.cve.org/CVERecord?id=CVE-2015-1197 Référence CVE CVE-2017-1000383 https://www.cve.org/CVERecord?id=CVE-2017-1000383 Référence CVE CVE-2017-6519 https://www.cve.org/CVERecord?id=CVE-2017-6519 Référence CVE CVE-2020-12413 https://www.cve.org/CVERecord?id=CVE-2020-12413 Référence CVE CVE-2021-25317 https://www.cve.org/CVERecord?id=CVE-2021-25317 Référence CVE CVE-2021-31535 https://www.cve.org/CVERecord?id=CVE-2021-31535 Référence CVE CVE-2021-33430 https://www.cve.org/CVERecord?id=CVE-2021-33430 Référence CVE CVE-2021-34141 https://www.cve.org/CVERecord?id=CVE-2021-34141 Référence CVE CVE-2021-3927 https://www.cve.org/CVERecord?id=CVE-2021-3927 Référence CVE CVE-2021-3928 https://www.cve.org/CVERecord?id=CVE-2021-3928 Référence CVE CVE-2021-3968 https://www.cve.org/CVERecord?id=CVE-2021-3968 Référence CVE CVE-2021-3973 https://www.cve.org/CVERecord?id=CVE-2021-3973 Référence CVE CVE-2021-3974 https://www.cve.org/CVERecord?id=CVE-2021-3974 Référence CVE CVE-2021-4136 https://www.cve.org/CVERecord?id=CVE-2021-4136 Référence CVE CVE-2021-4166 https://www.cve.org/CVERecord?id=CVE-2021-4166 Référence CVE CVE-2021-4173 https://www.cve.org/CVERecord?id=CVE-2021-4173 R

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0524Multiples vulnérabilités dans VMware Tanzu

d?id=CVE-2021-26220 Référence CVE CVE-2021-26221 https://www.cve.org/CVERecord?id=CVE-2021-26221 Référence CVE CVE-2021-26222 https://www.cve.org/CVERecord?id=CVE-2021-26222 Référence CVE CVE-2021-30485 https://www.cve.org/CVERecord?id=CVE-2021-30485 Référence CVE CVE-2021-31229 https://www.cve.org/CVERecord?id=CVE-2021-31229 Référence CVE CVE-2021-31347 https://www.cve.org/CVERecord?id=CVE-2021-31347 Référence CVE CVE-2021-31348 https://www.cve.org/CVERecord?id=CVE-2021-31348 Référence CVE CVE-2021-31598 https://www.cve.org/CVERecord?id=CVE-2021-31598 Référence CVE CVE-2021-33430 https://www.cve.org/CVERecord?id=CVE-2021-33430 Référence CVE CVE-2021-34141 https://www.cve.org/CVERecord?id=CVE-2021-34141 Référence CVE CVE-2021-37501 https://www.cve.org/CVERecord?id=CVE-2021-37501 Référence CVE CVE-2021-45829 https://www.cve.org/CVERecord?id=CVE-2021-45829 Référence CVE CVE-2021-45830 https://www.cve.org/CVERecord?id=CVE-2021-45830 Référence CVE CVE-2021-45832 https://www.cve.org/CVERecord?id=CVE-2021-45832 Référence CVE CVE-2021-45833 https://www.cve.org/CVERecord?id=CVE-2021-45833 Référence CVE CVE-2021-45943 https://www.cve.org/CVERecord?id=CVE-2021-45943 Référence CVE CVE-2021-46242 https://www.cve.org/CVERecord?id=CVE-2021-46242 Référence CVE CVE-2021-46243 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0670Multiples vulnérabilités dans Splunk Machine Learning Toolkit

on for Scientific Computing antérieures à 4.2.1 Résumé De multiples vulnérabilités ont été découvertes dans Splunk Machine Learning Toolkit. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Splunk SVD-2024-0801 du 12 août 2024 https://advisory.splunk.com/advisories/SVD-2024-0801 Référence CVE CVE-2020-28473 https://www.cve.org/CVERecord?id=CVE-2020-28473 Référence CVE CVE-2020-28975 https://www.cve.org/CVERecord?id=CVE-2020-28975 Référence CVE CVE-2021-34141 https://www.cve.org/CVERecord?id=CVE-2021-34141 Référence CVE CVE-2022-25882 https://www.cve.org/CVERecord?id=CVE-2022-25882 Référence CVE CVE-2022-31799 https://www.cve.org/CVERecord?id=CVE-2022-31799 Référence CVE CVE-2022-40897 https://www.cve.org/CVERecord?id=CVE-2022-40897 Référence CVE CVE-2022-40899 https://www.cve.org/CVERecord?id=CVE-2022-40899 Référence CVE CVE-2022-45907 https://www.cve.org/CVERecord?id=CVE-2022-45907 Référence CVE CVE-2023-25399 https://www.cve.org/CVERecord?id=CVE-2023-25399 Référence CVE CVE-2023-2800 https://www.cve.org/CVERecord?id=CVE-2023-2800 Référence CVE CVE-2023-37920 https://www.cve.org/CVERecord?id=CV

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

cord?id=CVE-2020-7598 Référence CVE CVE-2020-7720 https://www.cve.org/CVERecord?id=CVE-2020-7720 Référence CVE CVE-2021-20180 https://www.cve.org/CVERecord?id=CVE-2021-20180 Référence CVE CVE-2021-22060 https://www.cve.org/CVERecord?id=CVE-2021-22060 Référence CVE CVE-2021-23386 https://www.cve.org/CVERecord?id=CVE-2021-23386 Référence CVE CVE-2021-28163 https://www.cve.org/CVERecord?id=CVE-2021-28163 Référence CVE CVE-2021-28164 https://www.cve.org/CVERecord?id=CVE-2021-28164 Référence CVE CVE-2021-28165 https://www.cve.org/CVERecord?id=CVE-2021-28165 Référence CVE CVE-2021-28169 https://www.cve.org/CVERecord?id=CVE-2021-28169 Référence CVE CVE-2021-34141 https://www.cve.org/CVERecord?id=CVE-2021-34141 Référence CVE CVE-2021-34428 https://www.cve.org/CVERecord?id=CVE-2021-34428 Référence CVE CVE-2021-34429 https://www.cve.org/CVERecord?id=CVE-2021-34429 Référence CVE CVE-2021-3533 https://www.cve.org/CVERecord?id=CVE-2021-3533 Référence CVE CVE-2021-3677 https://www.cve.org/CVERecord?id=CVE-2021-3677 Référence CVE CVE-2021-4083 https://www.cve.org/CVERecord?id=CVE-2021-4083 Référence CVE CVE-2021-41496 https://www.cve.org/CVERecord?id=CVE-2021-41496 Référence CVE CVE-2021-42581 https://www.cve.org/CVERecord?id=CVE-2021-42581 Référence CVE CVE-2021-43138 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-016458NumPy における不適切な比較に関する脆弱性

NumPy には、不適切な比較に関する脆弱性が存在します。

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
n/a
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.
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 17 Dec 2021 · Last source change 4 Aug 2024, 00:05 UTC · CWE-697 · Incorrect Comparison

CVE recordCVE.org · 5.1
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-0151
Product sourceUnavailable
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
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 ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2021-0151↗Public exploit reference↗Patch or update 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-34141 · cve.blacktree.nl