Fortify On Demand UploaderApplication · Jenkins
CVE-2019-1003046
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 cross-site request forgery vulnerability in Jenkins Fortify on Demand Uploader Plugin 3.0.10 and earlier allows attackers to initiate a connection to an attacker-specified server.
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 confidenceCSRF vulnerability in Jenkins Fortify on Demand Uploader Plugin versions 3.0.10 and earlier allows authenticated users to be tricked into initiating connections to attacker-controlled servers. The plugin lacks proper CSRF token validation, enabling attackers to craft malicious requests that execute via a victim's authenticated session.
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
Fortify On Demand UploaderApplication
<= 3.0.10CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 Fortify on Demand Uploader plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Fortify on Demand Uploader' or check the plugin directory for the presence of the fortify-on-demand-uploader plugin filesAffected if The plugin is listed as installed in Jenkins
-
Check the installed plugin versionIn the Installed Plugins list, locate the Fortify on Demand Uploader plugin and note the version number displayedAffected if The version is 3.0.10 or earlier
-
Verify plugin configuration existsNavigate to the Fortify on Demand Uploader section in Jenkins configuration (typically under Manage Jenkins > Configure System or project configuration) to confirm the plugin has been configured with an endpointAffected if The plugin has been configured with a Fortify on Demand server URL or API credentials
-
Confirm authenticated user accessReview Jenkins user permissions and active sessions to determine if users with access to the plugin's functionality existAffected if Any authenticated user with permission to use the Fortify on Demand Uploader feature is present in the Jenkins instance
You are affected if the Fortify on Demand Uploader plugin is installed at version 3.0.10 or earlier and has been configured for use, enabling CSRF attacks against authenticated sessions.
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 Fortify on Demand Uploader Plugin to version 3.0.11 or later. Additionally, ensure global Jenkins CSRF protection ( crumb ) is enabled under Manage Jenkins > Configure Global Security.
Fix this in Fortify On Demand Uploader
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003046 — 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-1003046 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