CVE-2019-6446Not scoredCWE-502

CVE-2019-6446: Numpy vulnerability

Numpy

Fixed in 1.16.3 · Affected: Numpy before 1.16.3 · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

27.3%probability of exploitation in the next 30 days

98th percentile

050100

Higher than 98% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

An issue was discovered in NumPy before 1.16.3. It uses the pickle Python module unsafely, which allows remote attackers to execute arbitrary code via a crafted serialized object, as demonstrated by a numpy.load call. NOTE: third parties dispute this issue because it is a behavior that might have legitimate applications in (for example) loading serialized Python object arrays from trusted and authenticated sources.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Deserialization of Untrusted Data · Deserialization and Object Injection
Vendor: Numpy
Published: January 2019
Band: Likely to be exploited (10% or more), January 2019

CoverageNo articles yet

No CyberSIXT article names CVE-2019-6446 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

1 more reference is in the CVE record.