Jenkins Gogs Plugin 1.0.15 and earlier uses a non-constant time comparison function when checking whether the provided and expected webhook token are equal, potentially allowing attackers to use statistical methods to obtain a valid webhook token.
Product
org.jenkins-ci.plugins/gogs-webhook vulnerabilities
4 published CVES affecting org.jenkins-ci.plugins/gogs-webhook, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 4
- Critical
- 0
- High
- 1
- Medium
- 3
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest org.jenkins-ci.plugins/gogs-webhook CVEs
Newest publication first
-
MediumCVSS 5.3 EPSS 0.68%
-
CVE-2023-40348 Jenkins Gogs Plugin vulnerable to unsafe default behavior and information disclosure
PublishedMediumCVSS 5.3 EPSS 0.65%The webhook endpoint in Jenkins Gogs Plugin 1.0.15 and earlier provides unauthenticated attackers information about the existence of jobs in its output.
-
CVE-2023-40349 Jenkins Gogs Plugin vulnerable to unsafe default behavior and information disclosure
PublishedMediumCVSS 5.3 EPSS 0.68%Jenkins Gogs Plugin 1.0.15 and earlier improperly initializes an option to secure its webhook endpoint, allowing unauthenticated attackers to trigger builds of jobs.
-
HighCVSS 8.8 EPSS 1.7%
Jenkins Gogs Plugin stored credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.