# CVE-2022-39309: GoCD server secret encryption/decryption key leaked to agents during material serialization

> A compromised GoCD agent can leak the server's symmetric encryption key, allowing attackers to decrypt secrets intended for other agents or environments.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-f9qg-xcxq-cgv9

## What is CVE-2022-39309?

CVE-2022-39309 is a medium-severity vulnerability in gocd, published on 14 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

GoCD is a continuous delivery server. GoCD helps you automate and streamline the build-test-release cycle for continuous delivery of your product. GoCD versions prior to 21.1.0 leak the symmetric key used to encrypt/decrypt any secure variables/secrets in GoCD configuration to authenticated agents. A malicious/compromised agent may then expose that key from memory, and potentially allow an attacker the ability to decrypt secrets intended for other agents/environments if they also are able to obtain access to encrypted configuration values from the GoCD server. This issue is fixed in GoCD version 21.1.0. There are currently no known workarounds.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-499 (Serializable Class Containing Sensitive Data), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-39309?

It affects 1 product.


Products: Thoughtworks Gocd.

## How do I fix CVE-2022-39309?

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

## Is CVE-2022-39309 being exploited?

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

## Other vulnerabilities in gocd

- [CVE-2021-43290](https://insights.sbomify.com/CVE-2021-43290/): Path traversal in n/a (critical 9.8)
- [CVE-2021-44659](https://insights.sbomify.com/CVE-2021-44659/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2024-56320](https://insights.sbomify.com/CVE-2024-56320/): GoCD vulnerable to admin privilege escalation by a malicious internal/existing authenticated user (critical 9.4)
- [CVE-2022-39311](https://insights.sbomify.com/CVE-2022-39311/): Compromised agents may be able to execute remote code on GoCD Server (critical 9.1)
- [CVE-2022-29184](https://insights.sbomify.com/CVE-2022-29184/): Command Injection/Argument Injection in GoCD (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39309 and fix it if it is affected.

What it is: CVE-2022-39309 is a medium-severity vulnerability in gocd, published on 14 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-39309 in the wild and no public exploit code.

Affected product: gocd. 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-2022-39309/ (Markdown: https://insights.sbomify.com/CVE-2022-39309/index.md)
```

## Sources

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

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