Skip to content
Fencer Vulns
critical 9.8

CVE-2018-17825 json

An issue was discovered in AdPlug 2.3.1.

published 2018-10-01 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-9571

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

An issue was discovered in AdPlug 2.3.1. There are several double-free vulnerabilities in the CEmuopl class in emuopl.cpp because of a destructor's two OPLDestroy calls, each of which frees TL_TABLE, SIN_TABLE, AMS_TABLE, and VIB_TABLE.

Patch / fix

  • adplug Debian 14, Debian 13, Debian 12 2.2.1+dfsg3-1

debian advisories DEBIAN-CVE-2018-17825

  • adplug Ubuntu 16.04 LTS 2.2.1+dfsg3-1~build0.16.04.1
  • adplug Ubuntu 18.04 LTS 2.2.1+dfsg3-1~build0.18.04.1

ubuntu advisories UBUNTU-CVE-2018-17825

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-17825 updated cvss 4.0

adplug: several double-free vulnerabilities in the CEmuopl class in emuopl.cpp

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.30% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/adplug/adplug/issues/67 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.