# CVE-2023-30519: Jenkins Quay.io trigger Plugin webhook endpoint can be accessed without authentication

> Unauthenticated attackers can trigger builds for specified repositories due to a missing permission check in the Jenkins Quay.io trigger Plugin.

- **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:** 12 Apr 2023
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-q2fc-9ww2-ggfj

## What is CVE-2023-30519?

CVE-2023-30519 is a medium-severity missing authorization vulnerability in Jenkins Quay.io trigger Plugin, published on 12 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A missing permission check in Jenkins Quay.io trigger Plugin 0.1 and earlier allows unauthenticated attackers to trigger builds of jobs corresponding to the attacker-specified repository.

Weakness: CWE-862 (Missing Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:quayio-trigger` | Maven | All versions to 0.1 | None |
| `org.jenkins-ci.plugins:quayio-trigger` | Maven | All versions to 0.1 | None |

Products: Jenkins Quay.io Trigger.

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

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

## Is CVE-2023-30519 being exploited?

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

## Other vulnerabilities in Jenkins Quay.io trigger Plugin

- [CVE-2023-30520](https://insights.sbomify.com/CVE-2023-30520/): Jenkins Quay.io trigger Plugin Cross-site Scripting vulnerability (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-30519 is a medium-severity missing authorization vulnerability in Jenkins Quay.io trigger Plugin, published on 12 Apr 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-30519 in the wild and no public exploit code.

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

## Sources

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

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