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

CVE-2012-1800 has a CVSS 2.0 base score of 6.1 (Medium). CVSS vector: AV:A/AC:L/Au:N/C:N/I:N/A:C. EPSS exploitation probability: 1.5%.

Scalance S Firmware CVE-2012-1800

MEDIUM

Buffer Overflow (CWE-119)

2012-04-18 cret@cert.org

Buffer Overflow Siemens Denial Of Service RCE Scalance S Firmware Scalance S602 Scalance S612 Scalance S613

6.1

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

6.1 MEDIUM

AV:A/AC:L/Au:N/C:N/I:N/A:C

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:A/AC:L/Au:N/C:N/I:N/A:C

Attack Vector

Adjacent

Attack Complexity

Low

Confidentiality

None

Integrity

None

Availability

Lifecycle Timeline

CVE Published

Apr 18, 2012 - 10:33 cve.org

MEDIUM 6.1

DescriptionCVE.org

Stack-based buffer overflow in the Profinet DCP protocol implementation on the Siemens Scalance S Security Module firewall S602 V2, S612 V2, and S613 V2 with firmware before 2.3.0.3 allows remote attackers to cause a denial of service (device outage) or possibly execute arbitrary code via a crafted DCP frame.

AnalysisAI

Stack-based buffer overflow in the Profinet DCP protocol implementation on the Siemens Scalance S Security Module firewall S602 V2, S612 V2, and S613 V2 with firmware before 2.3.0.3 allows remote. Rated medium severity (CVSS 6.1), this vulnerability is low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified as Buffer Overflow (CWE-119), which allows attackers to corrupt memory to execute arbitrary code or crash the application. Stack-based buffer overflow in the Profinet DCP protocol implementation on the Siemens Scalance S Security Module firewall S602 V2, S612 V2, and S613 V2 with firmware before 2.3.0.3 allows remote attackers to cause a denial of service (device outage) or possibly execute arbitrary code via a crafted DCP frame. Affected products include: Siemens Scalance S Firmware, Siemens Scalance S602, Siemens Scalance S612, Siemens Scalance S613. Version information: before 2.3.0.3.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.