Skip to content
Fencer Intel
medium 5.5

CVE-2022-35018 json

Advancecomp v2.3 was discovered to contain a segmentation fault.

published 4y ago modified 4mo ago also EUVD-2022-37916

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

Summary

Advancecomp v2.3 was discovered to contain a segmentation fault.

Patch / fix

  • advancecomp Debian 14, Debian 13, Debian 12 2.4-1

debian advisories DEBIAN-CVE-2022-35018

  • advancecomp Ubuntu 18.04 LTS 2.1-1ubuntu0.18.04.3
  • advancecomp Ubuntu 20.04 LTS 2.1-2.1ubuntu0.20.04.1
  • advancecomp Ubuntu 22.04 LTS 2.1-2.1ubuntu2.1
  • advancecomp Ubuntu Pro 16.04 LTS 1.20-1ubuntu0.2+esm2

ubuntu advisories UBUNTU-CVE-2022-35018

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

  • advancecomp Alpine 3.24, Alpine 3.23, Alpine 3.22 +4 more 2.4-r0

alpine advisories ALPINE-CVE-2022-35018

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-35018 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2022-35018 updated cvss 5.5

advancecomp: SEGV via invalid read memory access

  • Red Hat Enterprise Linux 7 advancecomp
    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

0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • drive.google.com https://drive.google.com/file/d/1ChqmPdrjId87582a-o5ogWyEI8goRVWJ/view?usp=sharing referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/Cvjark/Poc/blob/main/advancecomp/CVE-2022-35018.md referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

References

Sources

Fencer Intel 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.