Quay.Io Trigger
Vendor:
First CVE: Apr 12, 2023 · Active for 3 years
2
Total CVEs
More Total CVEs than 53% of tracked products
2.0
Avg CVEs / Year
Higher CVE frequency than 63% of tracked products
5.3
Avg CVSS
Higher Avg CVSS than 13% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Quay.Io Trigger over time
Volume of CVEsAvg CVSS Base Score
First CVE
Apr 12, 2023
3 years ago
Most Recent CVE
Apr 12, 2023
1,203 days ago
CVE Severity & Scoring
Quay.Io Trigger2 CVEs
100%
All CVEs352,785 CVEs
45%
40%
11%
Medium
Attack Vector
Local0 (0.0%)
Network2 (100.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low2 (100.0%)
High0 (0.0%)
Unknown0 (0.0%)
User Interaction
None1 (50.0%)
Unknown0 (0.0%)
Required1 (50.0%)
Privileges Required
Low1 (50.0%)
High0 (0.0%)
None1 (50.0%)
Unknown0 (0.0%)
Top CVEs
Signals from CVEs in this product scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2023-30519MEDIUM 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 repo | Apr 12, 2023 | 5.3 | 20 | NO | NO |
CVE-2023-30520MEDIUM Jenkins Quay.io trigger Plugin 0.1 and earlier does not limit URL schemes for repository homepage URLs submitted via Quay.io trigger webhooks, resulting in a stored cross-site scri | Apr 12, 2023 | 5.4 | 19 | NO | NO |
Exploit Exposure
Signals from CVEs in this product scope (2 CVEs).
CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%
Social Chatter
Signals from CVEs in this product scope (2 CVEs).
Media Mentions
Signals from CVEs in this product scope (2 CVEs).
Top CNAs Publishing CVEs For Quay.Io Trigger
Top CWEs
Versions
No cataloged versions.