dbcve.org
Trac PublisherApplication · Jenkins

CVE-2019-1003067

HIGH · 8.8 CVSS v3.1 Published 2019-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Jenkins Trac Publisher Plugin stores 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 · moderate confidence

The Jenkins Trac Publisher Plugin stores credentials (likely API tokens or authentication keys for Trac integration) in plain text within job config.xml files on the Jenkins master. These unencrypted credentials are accessible to any user with Extended Read permission on Jenkins jobs, or anyone with filesystem access to the Jenkins master.

MitigationRemove stored credentials from Trac Publisher Plugin job configurations and use Jenkins' built-in credentials binding mechanism instead; alternatively, upgrade the plugin if a patched version is available.

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
Trac PublisherApplication
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Trac Publisher Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Trac Publisher' in the list, or check the plugin directory $JENKINS_HOME/plugins for a trac-plugin folder
    Affected if The Trac Publisher plugin is present in the Jenkins installation
  2. Identify jobs using Trac Publisher
    Use Jenkins CLI or API to search for jobs containing 'tracPublisher' in their config.xml, or manually review job configurations in the web UI under each job's Configure page for a Trac Publisher section
    Affected if Any job has Trac Publisher configured as a post-build action
  3. Inspect job config.xml for plain text credentials
    Locate the job's config.xml file in $JENKINS_HOME/jobs/<job-name>/config.xml and open it in a text editor, or use Jenkins API: GET /job/<job-name>/config.xml
    Affected if The config.xml contains plaintext values in elements related to Trac settings such as password, apiKey, token, or authentication fields under the tracPublisher section
  4. Check filesystem access to config.xml
    Review file permissions on $JENKINS_HOME/jobs/*/config.xml files - any user or process with read access to these files can obtain stored credentials
    Affected if The config.xml files are readable by users or processes other than Jenkins administrators
  5. Verify Extended Read permission exposure
    Navigate to Manage Jenkins > Manage Users and check if any users or groups have Extended Read permission, which allows reading job config.xml content without full administrative access
    Affected if Non-admin users have Extended Read permission enabled in Jenkins security settings

A user is affected if the Trac Publisher Plugin is installed and any job on the Jenkins master uses Trac Publisher with stored credentials in plain text within the job's config.xml file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove stored credentials from Trac Publisher Plugin job configurations and use Jenkins' built-in credentials binding mechanism instead; alternatively, upgrade the plugin if a patched version is available.

Fix this in Trac Publisher Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1003067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1003067 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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