What is the severity of CVE-2017-6890?

CVE-2017-6890 has a high severity level due to its potential for causing a stack-based buffer overflow.

How do I fix CVE-2017-6890?

The recommended fix for CVE-2017-6890 is to upgrade to LibRaw-demosaic-pack-GPL2 version 0.18.2 or later.

What software is affected by CVE-2017-6890?

CVE-2017-6890 affects LibRaw-demosaic-pack-GPL2 versions prior to 0.18.2.

What type of vulnerability is CVE-2017-6890?

CVE-2017-6890 is classified as a boundary error vulnerability leading to a stack-based buffer overflow.

Can CVE-2017-6890 be exploited remotely?

Yes, CVE-2017-6890 can potentially be exploited remotely if an attacker can provide malicious input to the affected software.

Vulnerability/
CVE-2017-6890

critical

9.8

CWE

119

15/5/2017

5/8/2024

CVE-2017-6890: Buffer Overflow

First published: Mon May 15 2017(Updated: )

A boundary error within the "foveon_load_camf()" function (dcraw_foveon.c) when initializing a huffman table in LibRaw-demosaic-pack-GPL2 before 0.18.2 can be exploited to cause a stack-based buffer overflow.

Credit: PSIRT-CNA@flexerasoftware.com

Affected Software	Affected Version	How to fix
Libraw Libraw-demosaic-pack-gpl2	<=0.18.1

Remedy

https://github.com/LibRaw/LibRaw-demosaic-pack-GPL2/commit/194f592e205990ea8fce72b6c571c14350aca716

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-6890?
CVE-2017-6890 has a high severity level due to its potential for causing a stack-based buffer overflow.
How do I fix CVE-2017-6890?
The recommended fix for CVE-2017-6890 is to upgrade to LibRaw-demosaic-pack-GPL2 version 0.18.2 or later.
What software is affected by CVE-2017-6890?
CVE-2017-6890 affects LibRaw-demosaic-pack-GPL2 versions prior to 0.18.2.
What type of vulnerability is CVE-2017-6890?
CVE-2017-6890 is classified as a boundary error vulnerability leading to a stack-based buffer overflow.
Can CVE-2017-6890 be exploited remotely?
Yes, CVE-2017-6890 can potentially be exploited remotely if an attacker can provide malicious input to the affected software.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/remedy
agent/author
agent/weakness
agent/tags
agent/event
agent/first-publish-date
agent/description
agent/source
vendor/libraw
canonical/libraw libraw-demosaic-pack-gpl2
version/libraw libraw-demosaic-pack-gpl2/0.18.1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-6890?
CVE-2017-6890 has a high severity level due to its potential for causing a stack-based buffer overflow.
How do I fix CVE-2017-6890?
The recommended fix for CVE-2017-6890 is to upgrade to LibRaw-demosaic-pack-GPL2 version 0.18.2 or later.
What software is affected by CVE-2017-6890?
CVE-2017-6890 affects LibRaw-demosaic-pack-GPL2 versions prior to 0.18.2.
What type of vulnerability is CVE-2017-6890?
CVE-2017-6890 is classified as a boundary error vulnerability leading to a stack-based buffer overflow.
Can CVE-2017-6890 be exploited remotely?
Yes, CVE-2017-6890 can potentially be exploited remotely if an attacker can provide malicious input to the affected software.