Relution Enterprise Appstore PublisherApplication · Jenkins
CVE-2019-10281
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 Relution Enterprise Appstore Publisher 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 Relution Enterprise Appstore Publisher Plugin stores credentials in plaintext within its global configuration file on the Jenkins master node. Users who have file system access to the Jenkins master can read these configuration files and obtain the stored credentials without authentication.
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
Relution Enterprise Appstore PublisherApplication
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.
-
Confirm if Relution Enterprise Appstore Publisher plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect the JENKINS_HOME/plugins directory for a folder named 'relution-enterprise-appstore-publisher' or similar.Affected if Plugin is present in the list of installed plugins or as a directory in the plugins folder.
-
Locate the plugin global configuration fileCheck JENKINS_HOME/org.jenkinsci.plugins.relution for a config.xml file, or search for files containing 'relution' in JENKINS_HOME. Plugin configurations are typically stored in $JENKINS_HOME/org.jenkinsci.plugins.relution* or within plugin-specific subdirectories.Affected if Configuration directory or file exists for this plugin.
-
Inspect the configuration file for stored credentialsOpen the found configuration file in a text editor or use a command like 'cat' to view its contents. Look for fields containing username, password, apiKey, or similar credential-related parameters.Affected if Configuration file contains plaintext username, password, API key, or other credential values without encryption or masking.
-
Verify credentials are stored in plaintext rather than maskedCompare the stored values to expected credential patterns. Plaintext credentials will appear as readable text (e.g., actual password string) rather than masked characters or encrypted blobs.Affected if Credential fields contain readable, unmasked password or API key strings that could be directly used by an attacker.
If the Relution Enterprise Appstore Publisher plugin is installed and its configuration file contains plaintext (unencrypted, unmasked) credentials, the environment is affected by CVE-2019-10281.
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 dataImmediately rotate any credentials that may have been stored by this plugin. Restrict file system access to the Jenkins master and consider migrating to Jenkins' built-in credentials store, or use an alternative plugin that handles credentials securely.
Fix this in Relution Enterprise Appstore Publisher
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10281 — 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-10281 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