AssemblaApplication · Jenkins
CVE-2019-10420
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 Assembla 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 Assembla Plugin stores credentials in plaintext within its global configuration file on the Jenkins master. Users with filesystem access to the Jenkins master can read these unencrypted credentials, potentially gaining unauthorized access to Assembla services integrated with Jenkins.
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
AssemblaApplication
<= 1.4CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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 Assembla plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed, or list contents of $JENKINS_HOME/plugins directory to confirm the assembla plugin is presentAffected if The Assembla plugin is installed on the Jenkins master
-
Determine Assembla plugin versionCheck the plugin version through Jenkins UI (Manage Plugins > Installed > Assembla) or inspect the plugin's manifest file (MANIFEST.MF) located in $JENKINS_HOME/plugins/assembla/Affected if The installed version is 1.4 or earlier
-
Locate the global configuration fileExamine the Jenkins home directory for the Assembla plugin configuration file, typically found at $JENKINS_HOME/assembla-config.xml or within the Jenkins main config.xml under the assembla sectionAffected if A configuration file specific to the Assembla plugin exists in the Jenkins home directory
-
Inspect configuration file for plaintext credentialsOpen the Assembla configuration file using a text editor or command-line tool (cat, less) and search for credential fields (password, secret, token, api_key) - verify whether values appear in plaintext rather than encryptedAffected if Credentials such as passwords, API tokens, or secret keys are stored in plaintext (readable, unencrypted format) within the configuration file
A user is affected if the Assembla plugin version is 1.4 or earlier AND plaintext credentials are present in the plugin's global configuration file on the Jenkins filesystem.
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 dataRestrict filesystem access to the Jenkins master and rotate any credentials that may have been exposed. Consider upgrading to a patched version of the plugin or using Jenkins' built-in credentials storage mechanism instead.
Fix this in Assembla
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-10420 — 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-10420 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