CVE-2017-7279
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 unprivileged user of the Unitrends Enterprise Backup before 9.0.0 web server can escalate to root privileges by modifying the "token" cookie issued at login.
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 confidenceUnitrends Enterprise Backup versions prior to 9.0.0 contain an authentication bypass vulnerability where an unprivileged user can modify their 'token' cookie after login to escalate privileges to root on the web server.
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<= 8.2.0-8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Unitrends Enterprise Backup is installedLocate the Unitrends Enterprise Backup installation on the system, typically found in its default installation directory or by querying installed software packagesAffected if The product is present on the system
-
Determine the installed version of Unitrends Enterprise BackupCheck the installed version using the product's version command, help interface, or system information file. Compare the version number against the affected range (versions prior to 9.0.0, specifically <= 8.2.0-8)Affected if The installed version is 8.2.0-8 or earlier, or any version prior to 9.0.0
-
Verify the web interface is accessibleConfirm the Unitrends web management interface is enabled and reachable, as the vulnerability exists in the web server component where the token cookie is processedAffected if The web interface is enabled and accessible to users
-
Inspect the token cookie handling mechanismFor an authenticated session, observe the 'token' cookie value and verify whether client-side modification of the cookie value can influence privilege levels without server-side validationAffected if The token cookie value can be modified by the client without proper server-side validation, allowing privilege escalation
A system is affected if Unitrends Enterprise Backup version 8.2.0-8 or earlier is installed with the web interface enabled, and the token cookie lacks server-side validation.
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 Unitrends Enterprise Backup to version 9.0.0 or later, which implements proper server-side token validation to prevent cookie tampering and privilege escalation.
- Consultation3.0 h
- Implementation5.0 h
- Testing3.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 $3,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7279 — 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-7279 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