LiveActive security incident?Get immediate response
CVE Record

CVE-2018-5241: Symantec Advanced Secure Gateway (ASG) 6.6 and 6.7, and ProxySG 6.5, 6.6, and 6.7 are susceptible to a SAML...

Symantec Advanced Secure Gateway (ASG) 6.6 and 6.7, and ProxySG 6.5, 6.6, and 6.7 are susceptible to a SAML authentication bypass vulnerability. The products can be configured with a SAML authentication realm to authenticate network users in intercepted proxy traffic. When parsing SAML responses, ASG and ProxySG incorrectly handle XML nodes with comments. A remote attacker can modify a valid SAML response without invalidating its cryptographic signature. This may allow the attacker to bypass user authentication security controls in ASG and ProxySG. This vulnerability only affects authentication of network users in intercepted traffic. It does not affect administrator user authentication for the ASG and ProxySG management consoles.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This vulnerability lets an attacker tamper with a valid SAML login response in a way Symantec ASG or ProxySG may still accept. In affected SAML-authenticated proxy deployments, that can bypass user authentication for intercepted proxy traffic. The sources state it does not affect administrator access to management consoles. Exposure is limited to affected ASG or ProxySG versions configured with a SAML authentication realm for intercepted proxy traffic. Deployments not using SAML realms for this function are not shown as exposed in the provided sources. Treat this as a targeted remediation item for organizations using Symantec proxy SAML authentication. Business urgency is highest where ASG or ProxySG gates workforce internet or internal access. No active exploitation evidence is provided, but authentication bypass in a security gateway deserves timely validation. Mitigation focus: Check Symantec advisory SA167 for vendor-supported fixes or configuration guidance.; Inventory ASG and ProxySG versions 6.5, 6.6, and 6.7.; Identify deployments using SAML authentication realms for intercepted proxy traffic..

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

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access 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-2018-5241 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 CorporationAdvanced Secure Gateway (ASG)6.6, 6.7Listed
Symantec CorporationProxySG6.5, 6.6, 6.7Listed
Weakness

CWE details

No CWE listed

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