# CVE-2020-11936: gdbus setgid privilege escalation


- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 31 Jan 2025
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-rfvc-9gpm-pcp3, UBUNTU-CVE-2020-11936

## What is CVE-2020-11936?

CVE-2020-11936 is a low-severity vulnerability in Canonical Ltd. Apport, published on 31 Jan 2025. 

### Official description

gdbus setgid privilege escalation

## Which versions are affected by CVE-2020-11936?

It affects 1 product.


Products: Canonical Apport.

## How do I fix CVE-2020-11936?

Upgrade to a fixed version.

## Is CVE-2020-11936 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-11936 exists.

## Other vulnerabilities in Canonical Ltd. Apport

- [CVE-2021-25682](https://insights.sbomify.com/CVE-2021-25682/): apport improperly parses /proc/pid/status (high 8.8)
- [CVE-2021-25683](https://insights.sbomify.com/CVE-2021-25683/): apport improperly parses /proc/pid/stat (high 8.8)
- [CVE-2021-25684](https://insights.sbomify.com/CVE-2021-25684/): apport can be stalled by reading a FIFO (high 8.8)
- [CVE-2021-3899](https://insights.sbomify.com/CVE-2021-3899/): Race condition in Apport (high 7.8)
- [CVE-2022-1242](https://insights.sbomify.com/CVE-2022-1242/): Other in Apport (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11936 and fix it if it is affected.

What it is: CVE-2020-11936 is a low-severity vulnerability in Canonical Ltd. Apport, published on 31 Jan 2025. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-11936 exists.

Affected product: Canonical Ltd. Apport. 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-2020-11936/ (Markdown: https://insights.sbomify.com/CVE-2020-11936/index.md)
```

## Sources

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

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