Strix
26.1K

CVE-2017-13666

UnknownEPSS 0.38%

Last modified

CVE-2017-13666 is a vulnerability of currently unknown severity. An integer underflow vulnerability exists in pixel-a.asm, the x86 assembly code for planeClipAndMax() in MulticoreWare x265 through 2.5, as used in libbpg and other products. A small height value can cause an integer underflow, which leads to a crash. EPSS estimates a 0.38% chance of exploitation in the next 30 days.

Description

An integer underflow vulnerability exists in pixel-a.asm, the x86 assembly code for planeClipAndMax() in MulticoreWare x265 through 2.5, as used in libbpg and other products. A small height value can cause an integer underflow, which leads to a crash. This is a different vulnerability than CVE-2017-8906.

Metrics

EPSS Probability
0.38%

30.0th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
MulticorewareincX2650.1
MulticorewareincX2650.2
MulticorewareincX2650.3
MulticorewareincX2650.4
MulticorewareincX2650.4.1
MulticorewareincX2650.5
MulticorewareincX2650.6
MulticorewareincX2650.7
MulticorewareincX2650.8
MulticorewareincX2650.9
MulticorewareincX2651
MulticorewareincX2651.1
MulticorewareincX2651.2
MulticorewareincX2651.3
MulticorewareincX2651.4
MulticorewareincX2651.5
MulticorewareincX2651.6
MulticorewareincX2651.7
MulticorewareincX2651.8
MulticorewareincX2651.9
MulticorewareincX2652.0
MulticorewareincX2652.1
MulticorewareincX2652.2
MulticorewareincX2652.3
MulticorewareincX2652.4
MulticorewareincX2652.5

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-13666?
An integer underflow vulnerability exists in pixel-a.asm, the x86 assembly code for planeClipAndMax() in MulticoreWare x265 through 2.5, as used in libbpg and other products. A small height value can cause an integer underflow, which leads to a crash. This is a different vulnerability than CVE-2017-8906.
How severe is CVE-2017-13666?
Severity scoring for CVE-2017-13666 is pending analysis. The EPSS model estimates a 0.38% probability of exploitation in the next 30 days.
How do I fix CVE-2017-13666?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2017

View all 2017CVEs →

Are you affected by CVE-2017-13666?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST