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

CVE-2013-2784 has a CVSS 2.0 base score of 7.8 (High). CVSS vector: AV:N/AC:L/Au:N/C:N/I:N/A:C. EPSS exploitation probability: 22.7%.

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

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

Nano 10 Plc Firmware CVE-2013-2784

HIGH

Cryptographic Issues (CWE-310)

2013-07-10 ics-cert@hq.dhs.gov

Denial Of Service Nano 10 Plc Firmware Nano 10 Plc

7.8

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

7.8 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Confidentiality

None

Integrity

None

Availability

Lifecycle Timeline

CVE Published

Jul 10, 2013 - 22:55 cve.org

HIGH 7.8

DescriptionCVE.org

Triangle Research International (aka Tri) Nano-10 PLC devices with firmware before r81 use an incorrect algorithm for bounds checking of data in Modbus/TCP packets, which allows remote attackers to cause a denial of service (networking outage) via a crafted packet to TCP port 502.

AnalysisAI

Triangle Research International (aka Tri) Nano-10 PLC devices with firmware before r81 use an incorrect algorithm for bounds checking of data in Modbus/TCP packets, which allows remote attackers to. Rated high severity (CVSS 7.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 22.7%.

Technical ContextAI

This vulnerability is classified under CWE-310. Triangle Research International (aka Tri) Nano-10 PLC devices with firmware before r81 use an incorrect algorithm for bounds checking of data in Modbus/TCP packets, which allows remote attackers to cause a denial of service (networking outage) via a crafted packet to TCP port 502. Affected products include: Triplc Nano-10 Plc Firmware, Triplc Nano-10 Plc.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.