dbcve.org
FisheyeApplication · Atlassian

CVE-2017-16861

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-01
Fix available
A fix is available. Upgrade to 4.4.5 / 4.5.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
It was possible for double OGNL evaluation in certain redirect action and in WebWork URL and Anchor tags in JSP files to occur. An attacker who can access the web interface of Fisheye or Crucible or who hosts a website that a user who can access the web interface of Fisheye or Crucible visits, is able to exploit this vulnerability to execute Java code of their choice on systems that run a vulnerable version of Fisheye or Crucible. All versions of Fisheye and Crucible before 4.4.5 (the fixed version for 4.4.x) and from 4.5.0 before 4.5.2 (the fixed version for 4.5.x) are affected by this vulnerability.

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 confidence

This is a double OGNL (Object-Graph Navigation Language) injection vulnerability in Fisheye and Crucible that allows remote code execution. Certain redirect actions and WebWork URL/Anchor tags in JSP files evaluate OGNL expressions twice, enabling attackers to break out of intended context and execute arbitrary Java code on the server.

MitigationUpgrade Fisheye to version 4.4.5 or 4.5.2 or later per the affected version matrix. Until patched, restrict network access to the web interface to reduce exposure.

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
FisheyeApplication
Affected:< 4.4.5>= 4.5.0, < 4.5.2
CrucibleApplication
Affected:< 4.4.5>= 4.5.0, < 4.5.2

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Fisheye or Crucible is installed
    Look for installation directories such as $FISHEYE_HOME or $CRUCIBLE_HOME, or check running processes for 'fisheye' or 'crucible' Java processes
    Affected if Fisheye or Crucible software is present on the system
  2. Determine the installed Fisheye version
    Check the version file typically located at <install_dir>/ fisheye version.txt, or access the admin interface at /admin/admin-fisheye.htm and view the version information
    Affected if Version is less than 4.4.5, or between 4.5.0 and 4.5.1 (inclusive)
  3. Determine the installed Crucible version
    Check the version file typically located at <install_dir>/crucible version.txt, or access the admin interface and view the version information
    Affected if Version is less than 4.4.5, or between 4.5.0 and 4.5.1 (inclusive)
  4. Verify network exposure of the web interface
    Check firewall rules or network configuration to determine if the Fisheye/Crucible web ports (typically 8060 for Fisheye, 8080 for Crucible) are accessible from untrusted networks
    Affected if The web interface is exposed to the internet or untrusted internal networks

A user is affected if Fisheye or Crucible version is 4.5.0, 4.5.1, or any version below 4.4.5, and the web interface is network-accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 4.4.5 / 4.5.2 or later
Fixed in 4.4.54.5.2
Interim mitigation

Upgrade Fisheye to version 4.4.5 or 4.5.2 or later per the affected version matrix. Until patched, restrict network access to the web interface to reduce exposure.

Recommended fix High confidence

Upgrade to Fisheye/Crucible 4.4.5 (for 4.4.x branch) or 4.5.2 (for 4.5.x branch)

  1. Determine current Fisheye or Crucible version from the administration console or by checking the product footer
  2. If running a 4.4.x version before 4.4.5, plan upgrade to 4.4.5
  3. If running a 4.5.0 or 4.5.1 version, plan upgrade to 4.5.2
  4. Backup the current installation and database before upgrading
  5. Stop the Fisheye/Crucible service
  6. Download the appropriate fixed version from the Atlassian download center (4.4.5 or 4.5.2)
  7. Install the new version following Atlassian upgrade documentation
  8. Start the service and verify the upgrade was successful
Caveat Security patch releases typically contain only bug fixes and security fixes; review Atlassian release notes for any behavior changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fisheye Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-16861 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-16861 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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