Local Privilege Escalation Vulnerability in SARG Package

sarg Updated 02 Oct 2025

Summary

21/01/2020
N/A
Yes i
Unrated
Not published

DEBIAN-CVE-2019-18932: log.c in Squid Analysis Report Generator (sarg) through 2.3.11 allows local privilege escalation. Affects sarg versions < 2.4.0-1. Fixed in 2.4.0-1. 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

The Squid Analysis Report Generator (SARG) is a tool used for analyzing and reporting on Squid proxy server logs. It provides detailed reports on web usage, allowing administrators to monitor and manage internet usage effectively. However, versions prior to 2.4.0-1 of SARG are susceptible to a local privilege escalation vulnerability due to insecure handling of temporary directories.

Vulnerability Detail

The vulnerability exists in the log.c file of SARG versions up to 2.3.11, where it creates or reuses a temporary directory (/tmp/sarg) in an insecure manner. An attacker can exploit this by pre-creating the directory and placing symlinks within it, leading to a race condition. This can result in the corruption of files or the creation of new files in privileged file system locations, potentially allowing unauthorized access or control over sensitive data.

How To Fix

Minimum fixed version

2.4.0-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade sarg

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, administrators can change the default temporary directory to a more secure location or implement strict permissions on the /tmp/sarg directory to mitigate the risk of exploitation.

Conclusion

In summary, the local privilege escalation vulnerability in the SARG package poses significant risks to system security. It is crucial for users to update to the patched version to mitigate these risks. Implementing workarounds can provide temporary relief while awaiting updates.

See every vulnerability recorded for sarg →

Share this vulnerability

FAQ

The vulnerability can lead to local privilege escalation, allowing attackers to manipulate files in privileged locations, potentially compromising system security.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Yes, the vulnerability is patched in SARG version 2.4.0-1 and later. It is recommended to update to this version or higher.

If immediate updates are not possible, consider implementing workarounds such as changing the temporary directory or adjusting permissions to limit exposure.

More information about SARG and its functionalities can be found on its official documentation and community forums.

Related vulnerabilities

Recent vulnerabilities recorded for sarg.

How To Fix

Minimum fixed version

2.4.0-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade sarg

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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