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

CVE-2013-0657 has a CVSS 2.0 base score of 10.0 (Critical). CVSS vector: AV:N/AC:L/Au:N/C:C/I:C/A:C. EPSS exploitation probability: 61.4%.

Is there a public PoC exploit available for CVE-2013-0657?

Yes, a public proof-of-concept exploit is available for CVE-2013-0657. Prioritise patching immediately. EPSS: 61.4%.

Is there a patch available for CVE-2013-0657?

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

Interactive Graphical Scada System CVE-2013-0657

CRITICAL

Buffer Overflow (CWE-119)

2013-01-21 ics-cert@hq.dhs.gov

Buffer Overflow Schneider Electric RCE Interactive Graphical Scada System

10.0

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

10.0 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Jan 21, 2013 - 16:55 cve.org

CRITICAL 10.0

DescriptionCVE.org

AnalysisAI

Stack-based buffer overflow in Schneider Electric Interactive Graphical SCADA System (IGSS) 10 and earlier allows remote attackers to execute arbitrary code by sending TCP port-12397 data that does. Rated critical severity (CVSS 10.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 61.4%.

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 Schneider Electric Interactive Graphical SCADA System (IGSS) 10 and earlier allows remote attackers to execute arbitrary code by sending TCP port-12397 data that does not comply with a protocol. Affected products include: Schneider-Electric Interactive Graphical Scada System.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.