CVE-2014-5028
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 Original File and Patched File resources in Review Board 1.7.x before 1.7.27 and 2.0.x before 2.0.4 allow remote authenticated users to bypass intended access restrictions and obtain sensitive information from repository files by leveraging knowledge of database ids.
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 confidenceReview Board contains an Insecure Direct Object Reference (IDOR) vulnerability in the Original File and Patched File resources. Authenticated users can bypass intended access restrictions to read arbitrary repository files by directly referencing database IDs, exposing sensitive information from repositories they should not have access to.
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> 1.7.0, < 1.7.27>= 2.0, < 2.0.4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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 Review Board versionLog into the Review Board admin interface and navigate to the About page, or run 'rb-site --version' if you have command-line access to the installation directory. Alternatively, check the installed package version via your package manager or pip.Affected if The installed version is greater than 1.7.0 and less than 1.7.27, or greater than or equal to 2.0 and less than 2.0.4.
-
Confirm authentication is enabledCheck that user authentication is active in the admin interface under Authentication settings. The IDOR vulnerability requires an authenticated user session to exploit.Affected if Anonymous users cannot exploit this vulnerability; authentication must be enabled for exploitation to be possible.
-
Verify repository access controls existReview repository settings in the admin interface to confirm which users or groups have access to which repositories. Check if there are restricted private repositories configured.Affected if If private or restricted repositories exist and users from other groups can authenticate, the IDOR vulnerability could allow unauthorized file access.
-
Check API/file resource endpointsExamine whether the web API endpoints for diff files and patched files are accessible. These typically include paths like /api/review-requests/<id>/diffs/<revision>/files/ and associated file content endpoints.Affected if If these API endpoints are exposed to authenticated users without proper authorization checks on the specific file ID requested, the environment is vulnerable.
A user is affected if they run a Review Board version in the vulnerable ranges and have repositories with access restrictions that could be bypassed via direct database ID references in file API endpoints.
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 data1.7.272.0.4
Upgrade Review Board to version 1.7.27 or later (for 1.7.x) or 2.0.4 or later (for 2.0.x) which implements proper authorization checks on file resources.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5028 — 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-2014-5028 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