CVE-2023-30519
First published: Wed Apr 12 2023(Updated: )
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.
Credit: jenkinsci-cert@googlegroups.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Jenkins Quay.io Trigger | <=0.1 | |
| <=0.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2023-30519?
CVE-2023-30519 is classified as a medium severity vulnerability.
How do I fix CVE-2023-30519?
To fix CVE-2023-30519, update the Jenkins Quay.io Trigger Plugin to version 0.1.1 or later.
Who is affected by CVE-2023-30519?
CVE-2023-30519 affects all users of Jenkins Quay.io Trigger Plugin version 0.1 and earlier.
What could an attacker do with CVE-2023-30519?
An attacker could trigger builds of jobs by specifying their desired repository due to the missing permission check.
Is authentication required to exploit CVE-2023-30519?
No, CVE-2023-30519 can be exploited by unauthenticated attackers.
- collector/nvd-index
- agent/references
- agent/type
- agent/first-publish-date
- agent/weakness
- agent/author
- agent/description
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/severity
- agent/source
- agent/tags
- agent/softwarecombine
- agent/event
- vendor/jenkins
- canonical/jenkins quay.io trigger
- version/jenkins quay.io trigger/0.1