Heap-use-after-free vulnerability in ClamAV

clamav Updated 02 Oct 2025

Summary

06/08/2023
HIGH
No i
High
Not published

OSV-2023-650: Heap-use-after-free in yr_parser_lookup_loop_variable. Affects clamav versions >= 0037f5825b0b17a789c7eb29c9cb9a2d39c452bc. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

ClamAV is an open-source antivirus engine designed for detecting malicious software. It provides a command-line scanner, a database updater, and integration with various mail servers. The vulnerability affects ClamAV versions prior to commit 0037f5825b0b17a789c7eb29c9cb9a2d39c452bc.

Vulnerability Detail

The vulnerability, identified as OSV-2023-650, is a heap-use-after-free issue in the yr_parser_lookup_loop_variable function of ClamAV. This vulnerability can be triggered during the parsing of YARA rules files. An attacker could exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition.

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

There is no known workaround for this vulnerability at this time.

Conclusion

The heap-use-after-free vulnerability in ClamAV can be exploited to execute arbitrary code or cause a denial-of-service condition. It is crucial to update ClamAV to a patched version that includes the fix commit 0037f5825b0b17a789c7eb29c9cb9a2d39c452bc to mitigate the risk of exploitation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for clamav →

Share this vulnerability

FAQ

ClamAV is an open-source antivirus engine used for detecting malicious software.

A heap-use-after-free vulnerability occurs when a program attempts to access memory that has already been freed. This can lead to crashes, memory corruption, and potentially allow attackers to execute arbitrary code.

An attacker can exploit this vulnerability by crafting a malicious YARA rules file and tricking a user or system into scanning it with a vulnerable version of ClamAV. This can lead to arbitrary code execution or denial-of-service attacks.

Yes, a fix for this vulnerability is available in ClamAV versions that include commit 0037f5825b0b17a789c7eb29c9cb9a2d39c452bc. Users are advised to update their ClamAV installations to a patched version.

No, there are no known workarounds for this vulnerability at this time.

Related vulnerabilities

Recent vulnerabilities recorded for clamav.

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