JiraApplication · Atlassian
CVE-2018-5231
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 ForgotLoginDetails resource in Atlassian Jira before version 7.6.6, from version 7.7.0 before version 7.7.4, from version 7.8.0 before version 7.8.4 and from version 7.9.0 before version 7.9.2 allows remote attackers to perform a denial of service attack via sending requests to it.
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 ForgotLoginDetails resource in Atlassian Jira versions 7.6.5 and earlier, 7.7.0-7.7.3, 7.8.0-7.8.3, and 7.9.0-7.9.1 contains a vulnerability that allows remote attackers to cause denial of service by sending crafted requests to this endpoint, likely due to insufficient request handling or rate limiting.
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
JiraApplication
< 7.6.6
Jira ServerApplication
>= 7.7.0, < 7.7.4>= 7.8.0, < 7.8.4>= 7.9.0, < 7.9.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Determine installed Jira versionLog into Jira as an administrator and navigate to the Administration > System > System Info page, or access /secure/AdminHome.jspa and locate the Jira version number displayed there.Affected if The displayed version is lower than 7.6.6, or falls within 7.7.0-7.7.3, 7.8.0-7.8.3, or 7.9.0-7.9.1.
-
Identify ForgotLoginDetails endpoint availabilityAttempt to access the ForgotLoginDetails endpoint via a web request to a path such as /ForgotLoginDetails.jspa, /ForgotLoginDetails.jsp, or /plugins/servlet/forgotlogin (exact path varies by Jira deployment).Affected if The endpoint responds and is reachable from the network without authentication.
-
Verify if the instance is exposed externallyReview network configuration and firewall rules to determine whether the Jira web interface is accessible from untrusted networks or the public internet.Affected if Jira is exposed externally and the ForgotLoginDetails endpoint is reachable without authentication.
-
Confirm vulnerability applicabilityCross-reference the exact version identified in step 1 against the affected version ranges: < 7.6.6, 7.7.0-7.7.3, 7.8.0-7.8.3, or 7.9.0-7.9.1.Affected if The installed version matches any of these vulnerable ranges and the ForgotLoginDetails endpoint is accessible.
A user is affected if their Jira version falls within the vulnerable ranges AND the ForgotLoginDetails endpoint is accessible, allowing potential remote attackers to send crafted requests causing denial of service.
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 data7.6.67.7.47.8.4
Upgrade Jira to version 7.6.6, 7.7.4, 7.8.4, 7.9.2 or later. If immediate patching is not possible, consider temporarily restricting or rate-limiting access to the ForgotLoginDetails endpoint at the network level.
Fix this in Jira
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-2018-5231 — 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-2018-5231 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