# CVE-2023-39059: Code injection in ansible semaphore

> Remote attackers can execute arbitrary code in Ansible Semaphore by sending a crafted payload to the extra variables parameter.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2023
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-3r32-cp7v-5wq4

## What is CVE-2023-39059?

CVE-2023-39059 is a high-severity code injection vulnerability in n/a, published on 28 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue in ansible semaphore v.2.8.90 allows a remote attacker to execute arbitrary code via a crafted payload to the extra variables parameter.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

2 open source packages ship an affected version, including github.com/ansible-semaphore/semaphore. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ansible-semaphore/semaphore` | Go | All versions to 2.8.90 | None |
| `github.com/ansible-semaphore/semaphore` | Go | All versions to 2.8.90 | None |

Products: Ansible-Semaphore Ansible Semaphore.

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

No fix has been published for CVE-2023-39059 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-39059 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-28609](https://insights.sbomify.com/CVE-2023-28609/): Ansible Semaphore mishandles authentication (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39059 is a high-severity code injection vulnerability in n/a, published on 28 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-39059 exists.

Affected packages and fixed versions:
- github.com/ansible-semaphore/semaphore (Go): affected all versions up to 2.8.90; no fix listed
- github.com/ansible-semaphore/semaphore (Go): affected all versions up to 2.8.90; no fix listed

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

## Sources

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

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