BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2017
CVE-2017-17760High confidence

OpenCV 3.3.1 has a Buffer Overflow in the cv::PxMDecoder::readData function in grfmt_pxm.cpp, because an incorrect size value is used

n/a · n/a

6.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

OpenCV 3.3.1 has a Buffer Overflow in the cv::PxMDecoder::readData function in grfmt_pxm.cpp, because an incorrect size value is used.

What

OpenCV 3.3.1 has a Buffer Overflow in the cv::PxMDecoder::readData function in grfmt_pxm.cpp, because an incorrect size value is used.

Why

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

OpenCV 3.3.1 has a Buffer Overflow in the cv::PxMDecoder::readData function in grfmt_pxm.cpp, because an incorrect size value is used.

Why

The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

How

An attacker operating through a network path may attempt exploitation without authentication after a 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 → Improper Restriction of Operations within the Bounds of a Memory Buffer → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
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-119

CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer. The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

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:R/S:U/C:N/I:N/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.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.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.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-119
A

Official authority intelligence

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

CERT-FR · French · CERTFR-2019-AVI-045Multiples vulnérabilités dans Google Android

versions n'intégrant pas le correctif de sécurité du 5 février 2019 Résumé De multiples vulnérabilités ont été découvertes dans Google Android. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service et une atteinte à la confidentialité des données. Solution 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é Android du 4 février 2019 https://source.android.com/security/bulletin/2019-02-01.html Référence CVE CVE-2016-6684 https://www.cve.org/CVERecord?id=CVE-2016-6684 Référence CVE CVE-2017-17760 https://www.cve.org/CVERecord?id=CVE-2017-17760 Référence CVE CVE-2017-18009 https://www.cve.org/CVERecord?id=CVE-2017-18009 Référence CVE CVE-2018-10879 https://www.cve.org/CVERecord?id=CVE-2018-10879 Référence CVE CVE-2018-11262 https://www.cve.org/CVERecord?id=CVE-2018-11262 Référence CVE CVE-2018-11268 https://www.cve.org/CVERecord?id=CVE-2018-11268 Référence CVE CVE-2018-11275 https://www.cve.org/CVERecord?id=CVE-2018-11275 Référence CVE CVE-2018-11280 https://www.cve.org/CVERecord?id=CVE-2018-11280 Référence CVE CVE-2018-11289 https://www.cve.org/CVERecord?id=CVE-2018-11289 Référence CVE CVE-2018-11820 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2018-AVI-067Multiples vulnérabilités dans Google Android

d?id=CVE-2017-13236 Référence CVE CVE-2017-13238 https://www.cve.org/CVERecord?id=CVE-2017-13238 Référence CVE CVE-2017-13247 https://www.cve.org/CVERecord?id=CVE-2017-13247 Référence CVE CVE-2017-14884 https://www.cve.org/CVERecord?id=CVE-2017-14884 Référence CVE CVE-2017-14910 https://www.cve.org/CVERecord?id=CVE-2017-14910 Référence CVE CVE-2017-15265 https://www.cve.org/CVERecord?id=CVE-2017-15265 Référence CVE CVE-2017-15817 https://www.cve.org/CVERecord?id=CVE-2017-15817 Référence CVE CVE-2017-15820 https://www.cve.org/CVERecord?id=CVE-2017-15820 Référence CVE CVE-2017-15829 https://www.cve.org/CVERecord?id=CVE-2017-15829 Référence CVE CVE-2017-17760 https://www.cve.org/CVERecord?id=CVE-2017-17760 Référence CVE CVE-2017-17761 https://www.cve.org/CVERecord?id=CVE-2017-17761 Référence CVE CVE-2017-17762 https://www.cve.org/CVERecord?id=CVE-2017-17762 Référence CVE CVE-2017-17764 https://www.cve.org/CVERecord?id=CVE-2017-17764 Référence CVE CVE-2017-17765 https://www.cve.org/CVERecord?id=CVE-2017-17765 Référence CVE CVE-2017-17767 https://www.cve.org/CVERecord?id=CVE-2017-17767 Référence CVE CVE-2017-17770 https://www.cve.org/CVERecord?id=CVE-2017-17770 Référence CVE CVE-2017-6258 https://www.cve.org/CVERecord?id=CVE-2017-6258 Référence CVE CVE-2017-6279 https://www.cve.org/CVERecord?id=CVE

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

OpenCV には、バッファエラーの脆弱性が存在します。

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.
Patch available
Affected
n/a: 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
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
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 29 Dec 2017 · Last source change 5 Aug 2024, 20:59 UTC · CWE-119 · Improper Restriction of Operations within the Bounds of a Memory Buffer

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-09-01
European sourceENISA EUVD · EUVD-2021-2215
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from no authoritative guidance recorded to authoritative remediation link · patch.
    Before
    no authoritative guidance recorded
    After
    authoritative remediation link · patch
    af854a3a-2127-422b-91ae-364da2661108
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    n/a · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    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.
    CNA
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    af854a3a-2127-422b-91ae-364da2661108
  4. SeveritySeverity changed from Unknown to Medium.
    Before
    Unknown
    After
    Medium
    NIST NVD
  5. CVSS scoreCVSS score changed from not recorded to 6.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H).
    Before
    not recorded
    After
    6.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H)
    NIST NVD
  6. ENISA EUVD mappingEUVD-2021-2215 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2021-2215"}
    ENISA EUVD
  7. Catalogue recordCVE added to the BlackTree catalogue.
    CNA
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-2017-17760 · cve.blacktree.nl