CVE-2015-2772
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 · uneditedSVM in Websense TRITON V-Series appliances before 8.0.0 allows attackers to upload arbitrary files via unspecified vectors.
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 · moderate confidenceThe SVM component in Websense TRITON V-Series appliances before version 8.0.0 contains an arbitrary file upload vulnerability. Attackers can upload arbitrary files to the system via unspecified vectors, potentially leading to remote code execution or system compromise.
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<= 7.7CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 Websense TRITON V-Series appliance installationCheck system inventory or network documentation for Websense V-Series appliance deployments. Look for device hostname, management interface, or product documentation referencing Websense TRITON.Affected if The system is a Websense TRITON V-Series appliance.
-
Determine installed software versionAccess the appliance management interface or check the system console for the TRITON version. Typically found in About or System Info section of the web UI, or via CLI command such as 'cat /etc/version' or 'version' command if available.Affected if The installed version is 7.7 or lower.
-
Verify SVM component is presentCheck if the SVM (Security Threat Manager or similar SVM module) component is installed or enabled on the appliance. This may be visible in the TRITON web interface under modules, components, or system services.Affected if The SVM component is installed and the version is 7.7 or lower.
-
Inspect SVM file upload interfaceIf accessible, examine the SVM component configuration or attempt to locate the file upload endpoint. Check for any unauthenticated or poorly authenticated upload paths in the web application structure.Affected if The SVM component allows unauthenticated or improperly authorized file uploads.
If the environment contains a Websense TRITON V-Series appliance running version 7.7 or lower with the SVM component enabled, it is likely affected by this arbitrary file upload vulnerability.
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 Websense TRITON V-Series appliances to version 8.0.0 or later to remediate this vulnerability. Additionally, restrict network access to the appliance management interface and implement proper authentication controls.
- 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-2015-2772 — 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-2015-2772 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