# CVE-2019-11675: Race condition in n/a

> Local attackers can exploit a race condition in logrotate interaction to gain root access via symlink insertion in the Debian Groonga HTTP server package.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-11675, GHSA-2p2g-mpv8-7wjq, UBUNTU-CVE-2019-11675

## What is CVE-2019-11675?

CVE-2019-11675 is a high-severity vulnerability in n/a, published on 2 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The groonga-httpd package 6.1.5-1 for Debian sets the /var/log/groonga ownership to the groonga account, which might let local users obtain root access because of unsafe interaction with logrotate. For example, an attacker can exploit a race condition to insert a symlink from /var/log/groonga/httpd to /etc/bash_completion.d. NOTE: this is an issue in the Debian packaging of the Groonga HTTP server.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2019-11675?

It affects 1 product.


Products: Groonga Groonga-Httpd.

## How do I fix CVE-2019-11675?

Apply the vendor's patch.

## Is CVE-2019-11675 being exploited?

There is no known exploitation of CVE-2019-11675 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11675 and fix it if it is affected.

What it is: CVE-2019-11675 is a high-severity vulnerability in n/a, published on 2 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-11675 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-11675/ (Markdown: https://insights.sbomify.com/CVE-2019-11675/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-11675
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-11675
- OSV: https://osv.dev/vulnerability/CVE-2019-11675

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-11675/
Summaries are generated and may contain mistakes; the official description above is the record.