What is the CVSS score of CVE-2013-0572?

CVE-2013-0572 has a CVSS 2.0 base score of 2.3 (Low). CVSS vector: AV:A/AC:M/Au:S/C:N/I:P/A:N. EPSS exploitation probability: 0.1%.

Application Support Facility CVE-2013-0572

LOW

Cross-site Scripting (XSS) (CWE-79)

2013-04-27 psirt@us.ibm.com

IBM Microsoft XSS Application Support Facility Document Connect For Application Support Facility

2.3

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

2.3 LOW

AV:A/AC:M/Au:S/C:N/I:P/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:A/AC:M/Au:S/C:N/I:P/A:N

Attack Vector

Adjacent

Attack Complexity

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Apr 27, 2013 - 03:16 cve.org

LOW 2.3

DescriptionCVE.org

Cross-site scripting (XSS) vulnerability in IBM Document Connect for Application Support Facility (aka DC4ASF) before 1.0.0.1218 in Application Support Facility (ASF) 3.4 for z/OS on Windows, Linux, and AIX allows remote authenticated users to inject content, and conduct phishing attacks, via unspecified vectors.

AnalysisAI

Cross-site scripting (XSS) vulnerability in IBM Document Connect for Application Support Facility (aka DC4ASF) before 1.0.0.1218 in Application Support Facility (ASF) 3.4 for z/OS on Windows, Linux,. Rated low severity (CVSS 2.3). No vendor patch available.

Technical ContextAI

This vulnerability is classified as Cross-Site Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. Cross-site scripting (XSS) vulnerability in IBM Document Connect for Application Support Facility (aka DC4ASF) before 1.0.0.1218 in Application Support Facility (ASF) 3.4 for z/OS on Windows, Linux, and AIX allows remote authenticated users to inject content, and conduct phishing attacks, via unspecified vectors. Affected products include: Ibm Application Support Facility, Ibm Document Connect For Application Support Facility. Version information: before 1.0.0.1218.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.