HockeyappApplication · Jenkins

CVE-2019-1003053

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 HockeyApp 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 · high confidence

The Jenkins HockeyApp Plugin stores credentials in plaintext within job config.xml files on the Jenkins master. Users with Extended Read permission (a common configuration) or anyone with filesystem access to the master can view these unencrypted credentials directly from the configuration files.

MitigationUpdate the HockeyApp Plugin to a version that encrypts credentials, and rotate any exposed credentials. Restrict Extended Read permission and limit filesystem access to the Jenkins master.

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
HockeyappApplication
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 if HockeyApp plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'HockeyApp', or inspect the plugin directory at $JENKINS_HOME/plugins/ for a hockeyapp folder
    Affected if The HockeyApp plugin is present in the Jenkins installation
  2. Identify jobs using the HockeyApp plugin
    Search job config.xml files for 'hockeyapp' references: grep -r 'hockeyapp' $JENKINS_HOME/jobs/*/config.xml or examine individual job configurations via Jenkins UI under job > Configure
    Affected if Any job configuration references the HockeyApp plugin or its related fields
  3. Inspect job config.xml for plaintext credentials
    Open the config.xml file of a job known to use HockeyApp (found at $JENKINS_HOME/jobs/<jobname>/config.xml) and look for <password> or <credentials> tags containing unencrypted credential strings
    Affected if The config.xml contains readable password or credential values in plain text rather than encrypted <secure> tags
  4. Check Extended Read permission configuration
    Navigate to Manage Jenkins > Manage Users and verify permissions at Manage Jenkins > Configure Global Security. Users with Extended Read can read job config.xml files without full job permissions
    Affected if Extended Read permission is granted to any user or group beyond administrators
  5. Verify filesystem access to config files
    Confirm that the Jenkins home directory ($JENKINS_HOME) and job config.xml files are accessible only to the Jenkins service account and authorized administrators
    Affected if Any non-admin system users or processes can read $JENKINS_HOME/jobs/*/config.xml files

A user is affected if the HockeyApp plugin is installed, any job uses it, and plaintext credentials or Extended Read permissions allow unauthorized credential disclosure.

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

Update the HockeyApp Plugin to a version that encrypts credentials, and rotate any exposed credentials. Restrict Extended Read permission and limit filesystem access to the Jenkins master.

Fix this in Hockeyapp 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-1003053 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1003053 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