CrucibleApplication · Atlassian
CVE-2019-15008
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/branchreview resource in Atlassian Fisheye and Crucible before version 4.7.3 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the reviewedBranch parameter.
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 reflected XSS vulnerability in Atlassian Fisheye and Crucible's /plugins/servlet/branchreview endpoint. The reviewedBranch parameter is not properly sanitized before being included in the HTTP response, allowing remote attackers to inject arbitrary HTML or JavaScript via malicious input.
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
CrucibleApplication
< 4.7.3
FisheyeApplication
< 4.7.3CVSS 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.1/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.
-
Identify installed Fisheye or Crucible versionLog into the application admin console and navigate to the 'About' or 'System Information' page, or check the version from the footer of any application pageAffected if The version displayed is lower than 4.7.3 for either product
-
Confirm the branchreview servlet is accessibleAttempt to access the /plugins/servlet/branchreview endpoint on your Fisheye or Crucible server using a web browser or HTTP clientAffected if The endpoint returns a valid HTTP response rather than a 404 error, indicating the servlet is enabled
-
Verify branch review functionality is configuredIn the admin interface, check if any repository has branch review features enabled under the repository settings or review configurationAffected if Branch review functionality is enabled for one or more repositories, making the vulnerable parameter functional
-
Test the reviewedBranch parameter for XSSSend a crafted request to /plugins/servlet/branchreview?reviewedBranch=<script>alert(1)</script> and observe whether the script tag is reflected unescaped in the responseAffected if The malicious payload is returned in the response body without HTML encoding, confirming the XSS vulnerability
You are affected if your Fisheye or Crucible version is below 4.7.3 and the branchreview servlet is accessible with branch review enabled, as the reviewedBranch parameter will reflect unsanitized input.
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 data4.7.3
Upgrade Atlassian Fisheye and Crucible to version 4.7.3 or later to remediate this vulnerability.
Fix this in Crucible
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15008 — 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-15008 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