Open StfApplication · Jenkins
CVE-2019-1003094
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 Open STF 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 Open STF Plugin version prior to the fix stored credentials in plaintext within its global configuration file on the Jenkins master. Any user with file system access to the Jenkins master could read these unencrypted credentials, leading to potential credential compromise.
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
Open StfApplication
<= 1.0.9CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 Open STF Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Open STF' or 'open-stf', or list installed plugins via CLI: jenkins-cli.jar or /pluginManager/api/json?tree=plugins[shortName,version]Affected if The Open STF Plugin appears in the installed plugins list
-
Check plugin versionIn the plugin manager, note the version column for Open STF Plugin, or query the plugin API for the version propertyAffected if The installed version is 1.0.9 or lower
-
Locate plugin configuration fileLook for Open STF plugin configuration files in the Jenkins home directory, typically under $JENKINS_HOME/plugins/open-stf/ or in org.openstf.* folders within $JENKINS_HOME/, or in the main config.xml if stored as a global configurationAffected if A configuration file for the Open STF Plugin exists on the Jenkins filesystem
-
Inspect for plaintext credentialsOpen the configuration file found and search for stored credentials, API keys, tokens, or passwords in plaintext (not base64-encoded, not encrypted)Affected if Credentials, passwords, API keys, or tokens appear in cleartext within the configuration file contents
-
Check configuration file permissionsRun 'ls -la' on the configuration file to view owner and permissions, or use 'getfacl' on WindowsAffected if The file is readable by users other than the Jenkins service account (permissions more permissive than 600 or equivalent)
User is affected if Open STF Plugin version 1.0.9 or lower is installed AND plaintext credentials are present in the plugin's configuration file with overly permissive file 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 dataUpgrade the Jenkins Open STF Plugin to a version that encrypts stored credentials. If no patched version is available, restrict filesystem access to the Jenkins master and consider removing the plugin until a fix is released.
Fix this in Open Stf
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003094 — 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-1003094 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