Hyper.sh CommonsApplication · Jenkins
CVE-2019-1003074
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 Hyper.sh Commons Plugin stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with 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 Hyper.sh Commons Plugin stores credentials unencrypted in plaintext within its global configuration file on the Jenkins master. Users with file system access to the Jenkins master can directly read these credentials from the configuration file.
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
Hyper.sh CommonsApplication
all versionsCVSS 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.
-
Verify Hyper.sh Commons plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and search for 'Hyper.sh Commons', or list installed plugins via CLI: jenkins-cli.jar or direct filesystem inspection of $JENKINS_HOME/plugins/Affected if The plugin appears in the list of installed plugins
-
Locate the plugin global configuration fileInspect $JENKINS_HOME for a configuration file associated with the Hyper.sh Commons plugin, typically named with the plugin identifier (such as org.jenkinsci.plugins.hyper shcommons.xml) in the Jenkins home directory or within the plugin's dedicated folder in $JENKINS_HOME/plugins/Affected if A configuration file for the Hyper.sh Commons plugin exists at the expected location
-
Inspect configuration file for plaintext credentialsOpen the configuration file identified in step 2 using a text editor or command-line tool (cat, type) and search for credential fields such as username, password, secretKey, accessKey, or similar sensitive data stored in cleartext formatAffected if Readable plaintext credentials (usernames, passwords, API keys, or secrets) are present in the configuration file content
-
Check filesystem permissions on the configuration fileRun 'ls -la' or 'icacls' on the configuration file to verify which OS users have read access to the fileAffected if Non-administrator users or the 'jenkins' service account user have read permissions to the configuration file containing plaintext credentials
A user is affected if the Hyper.sh Commons plugin is installed and its global configuration file contains readable plaintext credentials accessible to users with filesystem access.
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 dataMigrate credentials from plaintext storage to Jenkins' built-in encrypted credential store, and restrict filesystem access to the Jenkins master to only authorized administrators.
Fix this in Hyper.sh Commons
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003074 — 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-1003074 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