CVE-2019-18932
What it is
log.c in Squid Analysis Report Generator (sarg) through 2.3.11 allows local privilege escalation. By default, it uses a fixed temporary directory /tmp/sarg. As the root user, sarg creates this directory or reuses an existing one in an insecure manner. An attacker can pre-create the directory, and place symlinks in it (after winning a /tmp/sarg/denied.int_unsort race condition). The outcome will be corrupted or newly created files in privileged file system locations.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.0 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-59
- Record status
- Modified
Affected
- Squid Analysis Report Generator Project Squid Analysis Report Generator ≤ 2.3.11
- Opensuse Backports Sle 15.0
- Opensuse Leap 15.1
Attack profile CVSS 3.1 · 7.0
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2019-18932.md and follow it. Check whether this project is affected by CVE-2019-18932. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00051.html
- http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00063.html
- http://www.openwall.com/lists/oss-security/2020/01/20/6
- http://www.openwall.com/lists/oss-security/2020/01/20/6
- http://www.openwall.com/lists/oss-security/2020/01/20/6
- http://www.openwall.com/lists/oss-security/2020/01/20/6
- http://www.openwall.com/lists/oss-security/2020/01/27/1
- https://bugzilla.suse.com/show_bug.cgi?id=1150554
- https://seclists.org/oss-sec/2020/q1/23
- https://security.gentoo.org/glsa/202007-32
- https://sourceforge.net/projects/sarg/
- http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00051.html
- http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00063.html
- http://www.openwall.com/lists/oss-security/2020/01/20/6
- http://www.openwall.com/lists/oss-security/2020/01/20/6
- http://www.openwall.com/lists/oss-security/2020/01/20/6
- http://www.openwall.com/lists/oss-security/2020/01/20/6
- http://www.openwall.com/lists/oss-security/2020/01/27/1
- https://bugzilla.suse.com/show_bug.cgi?id=1150554
- https://seclists.org/oss-sec/2020/q1/23
- https://security.gentoo.org/glsa/202007-32
- https://sourceforge.net/projects/sarg/