Segmentation Fault in Advancecomp Package - CVE-2022-35019

advancecomp Updated 02 Oct 2025

Summary

29/08/2022
N/A
No i
Medium
5.5

CVE-2022-35019: Advancecomp v2.3 was discovered to contain a segmentation fault. Affects advancecomp versions < a543d4ce2897739d5ae44b89d26cd683b70c8d61. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Advancecomp is a suite of utilities designed for lossless compression of PNG files. It is widely used in various applications for optimizing image storage without sacrificing quality. The package is available across multiple Debian versions, including Debian 11, 12, and 13. This vulnerability poses a risk to users relying on Advancecomp for image processing, as it can lead to application crashes and data loss.

Vulnerability Detail

CVE-2022-35019 is a vulnerability discovered in Advancecomp version 2.3, which is characterized by a segmentation fault. This issue arises when the software attempts to access an invalid memory location, leading to unexpected behavior and potential crashes. The vulnerability can be exploited by malicious actors to disrupt services or cause denial of service, particularly in environments where Advancecomp is integrated into larger workflows.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If immediate upgrading is not feasible, users can temporarily avoid using the affected version of Advancecomp until a fix is applied. Additionally, consider isolating the application from critical systems to minimize the impact of potential crashes.

Conclusion

CVE-2022-35019 presents a significant risk to users of the Advancecomp package due to its potential to cause segmentation faults. It is crucial for users to upgrade to the latest version to ensure the integrity and reliability of their applications. Utilizing tools like Vulert can help in monitoring vulnerabilities effectively.

See every vulnerability recorded for advancecomp →

Share this vulnerability

FAQ

CVE-2022-35019 is a vulnerability in the Advancecomp package that causes a segmentation fault, potentially leading to application crashes.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected.

The segmentation fault can lead to application crashes, data loss, and service disruptions, particularly in production environments.

Yes, upgrading to Advancecomp version 2.4-1 or later mitigates the vulnerability.

Consider isolating the application from critical systems and refrain from using the affected version until an upgrade can be performed.

Related vulnerabilities

Recent vulnerabilities recorded for advancecomp.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback