CVE-2015-1490
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 · uneditedDirectory traversal vulnerability in the management console in Symantec Endpoint Protection Manager (SEPM) 12.1 before 12.1-RU6-MP1 allows remote authenticated users to read arbitrary files via a relative pathname in a client installation package.
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 confidenceDirectory traversal vulnerability in Symantec Endpoint Protection Manager 12.1 management console allows authenticated users to read arbitrary files by using relative pathnames (e.g., ../../) within client installation packages, bypassing intended directory restrictions.
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= 12.1.0CVSS 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
- Single
- Confidentiality
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:N/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 if Symantec Endpoint Protection Manager is installedCheck installed programs on the management server for 'Symantec Endpoint Protection Manager' or check Windows Services for 'Symantec Endpoint Protection Manager' serviceAffected if The product is present on the system
-
Determine the exact version of the installed management consoleAccess the management console, click Help > About, or check the version from the installer/registry under HKLM\Software\Symantec\Symantec Endpoint ProtectionManager\CurrentVersionAffected if The version is 12.1.0 (exact match)
-
Verify the management console is network-accessibleConfirm the management console port (default 8443 or 443) is listening and accessible to users who could authenticateAffected if The management console is exposed to authenticated users
-
Confirm authenticated access to client installation packages featureLog into the management console as a standard user and navigate to Clients > Install Packages or similar client deployment sectionAffected if Authenticated users can access the client package upload/download functionality
You are affected if Symantec Endpoint Protection Manager version 12.1.0 is installed with the management console accessible to authenticated users who can access the client installation packages feature.
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 to Symantec Endpoint Protection Manager 12.1-RU6-MP1 or later to obtain the patch. Additionally, restrict and monitor administrative access to the management console to reduce the attack surface.
- Consultation1.0 h
- Implementation4.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,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1490 — 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-1490 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