CVE-2017-7297
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 · uneditedRancher Labs rancher server 1.2.0+ is vulnerable to authenticated users disabling access control via an API call. This is fixed in versions rancher/server:v1.2.4, rancher/server:v1.3.5, rancher/server:v1.4.3, and rancher/server:v1.5.3.
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 confidenceRancher Server 1.2.0+ contains a vulnerability where authenticated users can disable access control through an API call, allowing privilege escalation and unauthorized access to cluster resources.
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.2.0, < 1.2.4>= 1.3.0, < 1.3.5>= 1.4.0, < 1.4.3>= 1.5.0, < 1.5.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Rancher Server versionCheck the Rancher UI footer or use the API endpoint /v1/settings/server-version to retrieve the exact version stringAffected if The version falls within >= 1.2.0 < 1.2.4, >= 1.3.0 < 1.3.5, >= 1.4.0 < 1.4.3, or >= 1.5.0 < 1.5.3
-
Verify access control statusNavigate to the Rancher UI under Admin > Access Control or query the API endpoint /v1/settings/authentication to confirm whether access control is enabledAffected if Access control is disabled when it should be enabled, indicating possible exploitation
-
Audit recent access control configuration changesReview Rancher audit logs or the API /v1/settings/authentication for any recent modifications to the authentication settings, including who made the change and whenAffected if Changes to authentication settings exist that were not initiated by an administrator
-
Check for unauthorized API accessInspect Rancher API access logs or audit trail for API calls to endpoints that modify access control settings, such as settings/authentication, from unexpected users or IPsAffected if API calls modifying access control were made by users who should not have that permission
A user is affected if their Rancher Server version is within any of the vulnerable ranges and access control has been disabled or modified without authorization.
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.2.41.3.51.4.3
Upgrade Rancher Server to version v1.2.4, v1.3.5, v1.4.3, v1.5.3 or later. Verify access control remains enabled after upgrade.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7297 — 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-7297 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