First published: Thu Jul 11 2019(Updated: )
Jenkins Gogs Plugin stored credentials unencrypted in job `config.xml` files on the Jenkins controller. These credentials could be viewed by users with Extended Read permission, or access to the Jenkins controller file system. Gogs Plugin now stores credentials encrypted.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
Jenkins Gogs | <=1.0.14 | |
Jenkins Gogs | ||
maven/org.jenkins-ci.plugins:gogs-webhook | <=1.0.14 | 1.0.15 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2019-10348 is high, with a severity value of 8.8.
CVE-2019-10348 allows local attackers to disclose sensitive information on affected installations of Jenkins Gogs.
Yes, authentication is required to exploit CVE-2019-10348.
The specific flaw within the Gogs plugin is the storage of credentials in plaintext.
An attacker can exploit CVE-2019-10348 by accessing and reading the plaintext stored credentials.