CrucibleApplication · Atlassian
CVE-2017-9512
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 mostActiveCommitters.do resource in Atlassian Fisheye and Crucible, before version 4.4.1 allows anonymous remote attackers to access sensitive information, for example email addresses of committers, as it lacked permission checks.
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 mostActiveCommitters.do resource in Atlassian Fisheye and Crucible versions before 4.4.1 lacked proper permission checks, allowing anonymous remote attackers to retrieve sensitive information such as committer email addresses without authentication.
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.4.0
FisheyeApplication
<= 4.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 if Atlassian Fisheye or Crucible is installedCheck your installed applications for Fisheye or Crucible products. Look for Fisheye or Crucible web applications in your environment, typically running on common web application servers or as standalone installations.Affected if Atlassian Fisheye or Crucible is present in the environment
-
Determine the installed Fisheye or Crucible versionAccess the Fisheye or Crucible administration interface and navigate to the 'About' or 'System Information' page to view the exact version number. Alternatively, check the installation directory for version files or the application banner at login.Affected if The version is 4.4.0 or earlier
-
Verify the mostActiveCommitters.do endpoint is accessibleAttempt to access the URL pattern 'https://[your-server]/rest-service-mostActiveCommitters.do' or similar paths ending with 'mostActiveCommitters.do' without providing any authentication credentials.Affected if The endpoint returns HTTP 200 and displays committer data without requiring login
-
Confirm sensitive information exposureInspect the response from the mostActiveCommitters.do endpoint to determine if it contains committer email addresses or other sensitive user information without authentication.Affected if The response includes email addresses or other sensitive data without requiring authentication
A user is affected if Fisheye or Crucible version 4.4.0 or earlier is installed and the mostActiveCommitters.do endpoint is accessible without authentication, exposing committer email addresses.
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 dataUpgrade to Fisheye/Crucible version 4.4.1 or later which includes the missing authorization checks, or implement access controls on the mostActiveCommitters.do endpoint if upgrading is not immediately feasible.
Fix this in Crucible
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9512 — 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-2017-9512 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