NeoloadApplication · Jenkins
CVE-2019-10440
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 NeoLoad Plugin 2.2.5 and earlier stored credentials unencrypted in its global configuration file and in job config.xml files on the Jenkins master where they could 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 confidenceThe Jenkins NeoLoad Plugin versions 2.2.5 and earlier stores credentials in plaintext within the global configuration file and individual job config.xml files. Users with Extended Read permission in Jenkins or physical/logical access to the master filesystem can view these unencrypted credentials.
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
NeoloadApplication
<= 2.2.5CVSS 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 NeoLoad Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for NeoLoad, or check the $JENKINS_HOME/plugins directory for a neoload folderAffected if NeoLoad Plugin is present on the Jenkins instance
-
Check NeoLoad Plugin versionView the plugin version in the UI plugin management screen, or inspect $JENKINS_HOME/plugins/neoload/META-INF/MANIFEST.MF for the Plugin-Version attributeAffected if Version is 2.2.5 or earlier
-
Locate and inspect global configuration for plaintext credentialsSearch for the global NeoLoad configuration file in $JENKINS_HOME (common paths include org.jenkinsci.plugins.neoload.GlobalNeoLoadConfig.xml or similar under the jenkins directory structure) and open it to look for any credential fields that appear as plaintext strings rather than encrypted valuesAffected if Plaintext credentials are present in the global configuration file
-
Inspect job config.xml files for plaintext credentialsSearch job config.xml files under $JENKINS_HOME/jobs/*/config.xml for neoload-related credential entries and verify whether values are stored as plaintext or in an encrypted formatAffected if Any job config.xml contains plaintext credentials related to NeoLoad integration
If the NeoLoad Plugin version is 2.2.5 or earlier AND plaintext credentials are found in either the global configuration file or any job config.xml files, the environment is affected by this CVE.
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 NeoLoad Plugin to a version that encrypts stored credentials and immediately rotate any credentials that may have been exposed through this vulnerability.
Fix this in Neoload
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10440 — 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-10440 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