ElectricflowApplication · Jenkins
CVE-2019-10336
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 · uneditedA reflected cross site scripting vulnerability in Jenkins ElectricFlow Plugin 1.1.6 and earlier allowed attackers able to control the output of the ElectricFlow API to inject arbitrary HTML and JavaScript in job configuration forms containing post-build steps provided by this plugin.
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 confidenceA reflected cross-site scripting vulnerability in Jenkins ElectricFlow Plugin versions 1.1.6 and earlier allows attackers who can control ElectricFlow API output to inject arbitrary HTML and JavaScript into job configuration forms containing post-build steps provided by this plugin.
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
ElectricflowApplication
<= 1.1.6CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Check ElectricFlow plugin versionNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'ElectricFlow' or 'electricflow' to see the installed versionAffected if The installed version is 1.1.6 or earlier
-
Verify plugin is activeIn the same plugin management page, confirm the ElectricFlow plugin shows as 'Enabled' or 'Active'Affected if Plugin is enabled and version is 1.1.6 or earlier
-
Identify jobs using ElectricFlow post-build stepsNavigate to Jenkins > Manage Jenkins > Script Console and run: Jenkins.instance.items.each { job -> job.builds.each { build -> build.actions.each { action -> if (action.class.simpleName == 'ElectricFlowBuildStep') { println job.fullName } } } } OR manually review job configurations for post-build steps with ElectricFlowAffected if Any job configuration contains ElectricFlow post-build steps and the plugin version is 1.1.6 or earlier
-
Check for unauthenticated or low-privilege API accessReview ElectricFlow plugin configuration at Jenkins > Manage Jenkins > Configure System > ElectricFlow and check if the ElectricFlow server API can be reached by users who can submit job configurationsAffected if Users with ability to control ElectricFlow API output (through job configs or API integration) exist in the environment and plugin version is vulnerable
Environment is affected if the ElectricFlow plugin version is 1.1.6 or earlier AND jobs contain ElectricFlow post-build steps where untrusted API output could be reflected in the job configuration forms.
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 ElectricFlow Plugin to a version newer than 1.1.6 and implement input sanitization on ElectricFlow API output before rendering in job configuration forms.
Fix this in Electricflow
Scoped from the published advisory
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10336 — 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-10336 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