What is the CVSS score of CVE-2012-3238?

CVE-2012-3238 has a CVSS 2.0 base score of 4.3 (Medium). CVSS vector: AV:N/AC:M/Au:N/C:N/I:P/A:N. EPSS exploitation probability: 0.5%.

Is there a public PoC exploit available for CVE-2012-3238?

Yes, a public proof-of-concept exploit is available for CVE-2012-3238. Prioritise patching immediately. EPSS: 0.5%.

Is there a patch available for CVE-2012-3238?

Yes, a patch is available for CVE-2012-3238. Update the affected software to the latest version immediately.

Security Gateway Software CVE-2012-3238

MEDIUM

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

2012-07-09 cve@mitre.org

XSS Security Gateway Software Security Gateway Unified Threat Management Software Unified Threat Management

4.3

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.3 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Jul 09, 2012 - 22:55 cve.org

MEDIUM 4.3

DescriptionCVE.org

Cross-site scripting (XSS) vulnerability in the Backup/Restore component in WebAdmin in Astaro Security Gateway before 8.305 allows remote attackers to inject arbitrary web script or HTML via the "Comment (optional)" field.

AnalysisAI

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 the Backup/Restore component in WebAdmin in Astaro Security Gateway before 8.305 allows remote attackers to inject arbitrary web script or HTML via the "Comment (optional)" field. Affected products include: Astaro Security Gateway Software, Astaro Security Gateway, Sophos Unified Threat Management Software, Sophos Unified Threat Management. Version information: before 8.305.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.