# CVE-2023-29403: Unsafe behavior in setuid/setgid binaries in runtime

> Go runtime fails to handle setuid/setgid binaries safely, potentially leaking register contents or allowing unexpected file access with elevated privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Jun 2023
- **Updated:** 13 Feb 2025
- **Also known as:** AZL-27112, AZL-27121, AZL-37301, AZL-37368, AZL-52789, AZL-79002, AZL-98901, BIT-golang-2023-29403, DEBIAN-CVE-2023-29403, GHSA-rxx3-4978-3cc9, GO-2023-1840, MINI-rv66-x88j-5xg2, OESA-2023-1404, UBUNTU-CVE-2023-29403

## What is CVE-2023-29403?

CVE-2023-29403 is a high-severity vulnerability in Fedoraproject Fedora, published on 8 Jun 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors. If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2023-29403?

2 open source packages ship an affected version, including golang and stdlib. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `golang` | Bitnami | All versions | 1.19.10, 1.20.5 |
| `stdlib` | Go | All versions | 1.19.10, 1.20.5 |

Products: Fedoraproject Fedora, Golang Go.

## How do I fix CVE-2023-29403?

Upgrade golang to a fixed version for your release line: 1.19.10 or 1.20.5.

## Is CVE-2023-29403 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29403 and fix it if it is affected.

What it is: CVE-2023-29403 is a high-severity vulnerability in Fedoraproject Fedora, published on 8 Jun 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-29403 in the wild and no public exploit code.

Affected packages and fixed versions:
- golang (Bitnami): affected all versions; fixed in 1.19.10, 1.20.5
- stdlib (Go): affected all versions; fixed in 1.19.10, 1.20.5

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-2023-29403/ (Markdown: https://insights.sbomify.com/CVE-2023-29403/index.md)
```

## Sources

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

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