CVE Intelligence
Medium Memory corruption exploit reference

CVE-2015-1239 — Double Free in Debian Debian Linux

Double free vulnerability in the j2k_read_ppm_v3 function in OpenJPEG before r2997, as used in PDFium in Google Chrome, allows remote attackers to cause a denial of service (process crash) via a crafted PDF.

Published Oct 18, 2017 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Chrome

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 1% (30-day exploitation probability)+9
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
1.04%
ahead of 63% of scored CVEs · Oct 14, 2026
Affects
Debian
Debian Linux and 2 more
CVSS base
6.5
Medium · 1 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Google Chrome, Uclouvain Openjpeg).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  5. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Debian Debian Linux version 8.0 Vulnerable NIST National Vulnerability Database
Google Chrome versions not specified by the source Vulnerable NIST National Vulnerability Database
Uclouvain Openjpeg < 2.1.1 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.5 CVSS 3.1 Medium 2.8 3.6 nvd@nist.gov via NIST National Vulnerability Database
4.3 CVSS 2.0 Medium 8.6 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-415 · Double Free

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 1.04%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Record published
    Oct 13, 2026
  • CVSS changed · 6.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2017
  • CVE published
    Oct 18, 2017 · Chrome

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

3 on the record

Elsewhere on this site

Debian
every CVE for this vendor
CWE-415
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-110172 Use after free in Media in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d
  • Medium CVE-2026-110170 Use after free in Bindings in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d
  • High CVE-2026-110171 Use after free in Media in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d
  • Critical CVE-2026-110165 Use after free in Core in Google Chrome on on Android prior to 155.0.8059.79 allowed a remote... 1d
  • High CVE-2026-110163 Use after free in DOM in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d
  • High CVE-2026-110164 Use after free in DOM in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2015-1239 is "Double Free in Debian Debian Linux", rated Medium. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 1.04% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.