LiveActive security incident?Get immediate response
CVE Record

CVE-2017-15527: Prior to ITMS 8.1 RU4, the Symantec Management Console can be susceptible to a directory traversal exploit,...

Prior to ITMS 8.1 RU4, the Symantec Management Console can be susceptible to a directory traversal exploit, which is a type of attack that can occur when there is insufficient security validation / sanitization of user-supplied input file names, such that characters representing "traverse to parent directory" are passed through to the file APIs.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Symantec Management Console before ITMS 8.1 RU4 was reported vulnerable to directory traversal. In plain terms, unsafe filename handling could let requests reference files outside the intended location. Business urgency depends on deployment exposure and access controls, which the provided sources do not specify. Organizations running Symantec Management Console versions prior to ITMS 8.1 RU4 are potentially exposed. Exposure is higher if the console is reachable by untrusted networks or broadly accessible internal users, but the sources do not confirm network reachability or authentication prerequisites. Prioritize inventory and upgrade verification for any remaining Symantec Management Console installations. The absence of severity and exploitation evidence lowers certainty, but management consoles are sensitive assets and should not remain on versions identified as vulnerable. Mitigation focus: Identify any Symantec Management Console deployments and installed ITMS release levels.; Upgrade systems running versions prior to ITMS 8.1 RU4 per vendor guidance.; Restrict console access to trusted administrative networks and users..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-15527 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Symantec CorporationSymantec Management ConsolePrior to ITMS 8.1 RU4Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.