GogsApplication · Jenkins
CVE-2019-10348
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Gogs Plugin stored SCM credentials in plaintext within job config.xml files on the Jenkins master. Users with Extended Read permission (a feature allowing broader job config visibility) or anyone with filesystem access to the Jenkins master could view these stored credentials in clear text.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GogsApplication
<= 1.0.14CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Gogs Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab, locate the Gogs Plugin, and note the version numberAffected if The installed version is 1.0.14 or lower
-
Locate job config.xml filesBrowse the Jenkins home directory (typically $JENKINS_HOME/jobs/<jobname>/config.xml) for each job configured to use Gogs SCMAffected if config.xml files exist for jobs using Gogs as the SCM source
-
Inspect for plaintext credentials in config.xmlOpen a job config.xml file and search within the <scm> or <credentials> section for unencrypted username/password strings - look for clear text passwords rather than encrypted <secret> entriesAffected if The config.xml contains visible plaintext passwords or usernames in the Gogs SCM configuration section
-
Check for Extended Read permission usageNavigate to Manage Jenkins > Manage Users and review user permissions, or inspect job configuration files for <useSecurity>true</useSecurity> with Extended Read enabled in matrix-based authorizationAffected if Extended Read permission is granted to users or groups who should not have visibility into job configuration details
If the Gogs Plugin version is 1.0.14 or lower AND any job config.xml files contain unencrypted credentials in plaintext, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRotate all credentials that may have been exposed through this vulnerability, update the Gogs Plugin to the latest version which encrypts credentials, and review user permissions for Extended Read access on sensitive jobs.
Fix this in Gogs
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10348 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10348 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data