Jira ServerApplication · Atlassian
CVE-2019-8451
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 · uneditedThe /plugins/servlet/gadgets/makeRequest resource in Jira before version 8.4.0 allows remote attackers to access the content of internal network resources via a Server Side Request Forgery (SSRF) vulnerability due to a logic bug in the JiraWhitelist class.
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 confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in Atlassian Jira's gadget framework. The /plugins/servlet/gadgets/makeRequest endpoint contains a logic flaw in the JiraWhitelist class that allows remote attackers to bypass whitelist restrictions and make requests to internal network resources, potentially exposing internal services, ports, and sensitive data behind firewalls.
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
Jira ServerApplication
>= 7.6.0, < 8.4.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
-
Identify Jira Server versionCheck the installed Jira version via the admin interface (Administration > System > Troubleshooting and support > System info) or by viewing the <Jira-installation>/atlassian-jira/WEB-INF/classes/application-info.json fileAffected if The installed version is 7.6.0 through 8.3.x (any version >= 7.6.0 but < 8.4.0)
-
Verify gadget framework is enabledConfirm the Atlassian Gadget Framework plugin is active by navigating to Administration > Manage apps > Gadgets in the Jira admin consoleAffected if The gadget framework plugin is enabled and running
-
Confirm endpoint accessibilityAttempt to access or check for the presence of the /plugins/servlet/gadgets/makeRequest endpoint by sending a request to your Jira base URL with this pathAffected if The endpoint responds (even with an error) indicating the servlet is accessible
-
Check network exposure of gadget servletReview web server or firewall configuration to determine if the /plugins/servlet/gadgets/ path is exposed to untrusted networks or the internetAffected if The endpoint is reachable from untrusted networks or the internet without network-level restrictions
You are affected if your Jira Server version is 7.6.0 or higher but lower than 8.4.0 AND the gadget framework is enabled AND the vulnerable endpoint is accessible to potential attackers.
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 data8.4.0
Upgrade Jira to version 8.4.0 or later to patch the SSRF vulnerability. As an interim measure, restrict access to the /plugins/servlet/gadgets/ path at the network perimeter or application level until the upgrade can be applied.
Fix this in Jira Server
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8451 — 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-8451 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