Skip to main content
No exploitation reportedFix available

CVE-2019-8379

No exploitation reported by the sources we read.

  • Published2019-02-17
  • Fixed in2.1
  • WeaknessCWE-476

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

An issue was discovered in AdvanceCOMP through 2.1. A NULL pointer dereference exists in the function be_uint32_read() located in endianrw.h. It can be triggered by sending a crafted file to a binary. It allows an attacker to cause a Denial of Service (Segmentation fault) or possibly have unspecified other impact when a victim opens a specially crafted file.

Timeline

dates in UTC
  1. 2019-02-1702:29CVE publishedNVD

Versions per branch

NVD
Advancemame advancecomp
BranchAffectedFixed in
2.1< 2.12.1
Debian debian linux
BranchAffectedFixed in
9.0= 9.0no fix published
Fedoraproject fedora
BranchAffectedFixed in
35.x= 35no fix published

3 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • advancecompUbuntu:Pro:16.04:LTSall versions · fixed in 1.20-1ubuntu0.2+esm1
  • advancecompUbuntu:18.04:LTSall versions · fixed in 2.1-1ubuntu0.18.04.2
  • advancecompRed Hat:enterprise_linux:7::workstationall versions · fixed in 0:1.15-21.el7and 1 other package
  • advancecompRed Hat:enterprise_linux:7::serverall versions · fixed in 0:1.15-21.el7and 1 other package
  • advancecompDebian:14all versions · fixed in 2.1-2.1
  • advancecompDebian:13all versions · fixed in 2.1-2.1
  • advancecompDebian:12all versions · fixed in 2.1-2.1
  • advancecompDebian:9all versions · fixed in 1.20-1+deb9u1

2 more package ranges on OSV.dev

Vendor advisories

  • CVE-2019-8379 Red Hat Product Security8 products fixed

    advancecomp: null pointer dereference in function be_uint32_read() in endianrw.h

  • RHSA-2019:2332 Red Hat Product Security8 products fixed

    Red Hat Security Advisory: advancecomp security update

Full record on NVD

Fix

  1. Update Advancemame advancecomp to 2.1
  2. Vendor fix Red Hat Product Security RHSA-2019:2332 · 8 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2019-02-17
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-422q-rpjc-cfgp

Frequently asked questions

What is CVE-2019-8379?

An issue was discovered in AdvanceCOMP through 2.1. A NULL pointer dereference exists in the function be_uint32_read() located in endianrw.h. It can be triggered by sending a crafted file to a binary. It allows an attacker to cause a Denial of Service (Segmentation fault) or possibly have unspecified other impact when a victim opens a specially crafted file.

Is CVE-2019-8379 actively exploited?

Active exploitation of CVE-2019-8379 has not been confirmed. Its EPSS score was 1.2% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-8379?

CVE-2019-8379 has a CVSS v3 base score of 7.8 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running advancecomp? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record