CVE-2017-16761
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 · uneditedAn Open Redirect vulnerability in Inedo BuildMaster before 5.8.2 allows remote attackers to redirect users to arbitrary web sites.
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 confidenceInedo BuildMaster before version 5.8.2 contains an Open Redirect vulnerability where the application accepts a user-controlled URL parameter and redirects users to that destination without proper validation. Attackers can craft malicious links that appear to originate from the legitimate BuildMaster domain, potentially tricking users into visiting phishing or malicious sites.
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< 5.8.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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.
-
Locate BuildMaster installation and versionCheck the installation directory for BuildMaster. Common paths include C:\Program Files\Inedo\BuildMaster or /opt/buildmaster. Look for a version file or check the application itself for its version number (typically accessible via the web UI or an about page).Affected if The installed version is found to be lower than 5.8.2 (e.g., 5.8.1, 5.7.x, 5.6.x, etc.)
-
Identify redirect-capable endpointsReview the BuildMaster web application for pages that accept a 'url', 'redirect', 'target', or similar parameter that could cause a redirect. Common areas include login pages, logout handlers, or action completion pages.Affected if Any endpoint exists that accepts a user-controlled URL parameter and performs a redirect without validating that the destination is internal to the application.
-
Test redirect behavior with a known external domainIf accessible, craft a test request to suspected redirect endpoints using an external domain (e.g., append ?url=http://example.com to suspected redirect handlers). Observe whether the application redirects to the external domain.Affected if The application redirects to the provided external URL instead of rejecting it or restricting redirects to internal paths.
You are affected if BuildMaster version is below 5.8.2 and the application contains redirect functionality that accepts unvalidated user-supplied URLs.
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 data5.8.2
Upgrade Inedo BuildMaster to version 5.8.2 or later to obtain the patched implementation that properly validates redirect targets.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16761 — 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-16761 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