# CVE-2023-46660: Non-constant time webhook token hash comparison in Jenkins Zanata Plugin

> Attackers can bypass webhook token validation in the Jenkins Zanata Plugin using timing attacks to obtain valid tokens.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-86j9-25m2-9w97

## What is CVE-2023-46660?

CVE-2023-46660 is a medium-severity vulnerability in Jenkins Zanata Plugin, published on 25 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jenkins Zanata Plugin 0.6 and earlier uses a non-constant time comparison function when checking whether the provided and expected webhook token hashes are equal, potentially allowing attackers to use statistical methods to obtain a valid webhook token.

Weakness: CWE-697 (Incorrect Comparison)

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

2 open source packages ship an affected version, including org.jenkins-ci.plugins:zanata. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:zanata` | Maven | All versions to 0.6 | None |
| `org.jenkins-ci.plugins:zanata` | Maven | All versions to 0.6 | None |

Products: Jenkins Zanata.

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

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

## Is CVE-2023-46660 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-46660 is a medium-severity vulnerability in Jenkins Zanata Plugin, published on 25 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-46660 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:zanata (Maven): affected all versions up to 0.6; no fix listed
- org.jenkins-ci.plugins:zanata (Maven): affected all versions up to 0.6; 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-46660/ (Markdown: https://insights.sbomify.com/CVE-2023-46660/index.md)
```

## Sources

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

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