360 FirelineApplication · Jenkins
CVE-2019-10466
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 · uneditedAn XML external entities (XXE) vulnerability in Jenkins 360 FireLine Plugin allows attackers with Overall/Read access to have Jenkins resolve external entities, resulting in the extraction of secrets from the Jenkins agent, server-side request forgery, or denial-of-service attacks.
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 confidenceAn XML external entities (XXE) vulnerability in Jenkins 360 FireLine Plugin allows authenticated users with Overall/Read permission to craft malicious XML containing external entity references. This enables attackers to extract secrets from Jenkins agents, perform server-side request forgery, or cause denial-of-service through malicious entity expansion.
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
360 FirelineApplication
<= 1.7.2CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Check if 360 FireLine plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or list files in $JENKINS_HOME/plugins/ directory and look for 'fireline' or '360-fireline' folderAffected if The plugin folder exists in the plugins directory or appears in the Installed plugins list
-
Identify the installed version of 360 FireLineCheck the plugin's manifest file: inspect $JENKINS_HOME/plugins/fireline/META-INF/MANIFEST.MF for the Implementation-Version, or in Jenkins UI view the plugin details which display the version numberAffected if The version is 1.7.2 or lower
-
Confirm the plugin is enabled and loadedIn Jenkins > Manage Jenkins > Manage Plugins > Installed, verify the 360 FireLine plugin shows as 'Enabled' or check $JENKINS_HOME/plugins/fireline/.enabled file exists, and the plugin is not marked as disabled in $JENKINS_HOME/pluginConfiguration.xmlAffected if The plugin is enabled and Jenkins has loaded it into memory
-
Verify user access controls for Overall/Read permissionNavigate to Jenkins > Manage Jenkins > Configure Global Security, and review which users or groups have Overall/Read permission. Check if any user with limited privileges (beyond just administrators) can access JenkinsAffected if Non-admin users or anonymous users have Overall/Read permission, which allows them to trigger XML parsing via the plugin
A user is affected if the 360 FireLine plugin version 1.7.2 or lower is installed, enabled, and the Jenkins instance grants Overall/Read permission to users who should not have it, allowing them to exploit the XXE vulnerability.
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 dataUpdate the 360 FireLine Plugin to a patched version that disables external entity processing in its XML parser, or remove/disable the plugin if not required.
Fix this in 360 Fireline
Scoped from the published advisory
- Consultation3.0 h
- Implementation3.0 h
- Testing2.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10466 — 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-10466 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