Menu

Star on GitHub · 3.2k

CVE-2013-0699

7.1 · HIGH

The Galil RIO-47100 Pocket PLC allows remote attackers to cause a denial of service via a session that includes "repeated requests."

Published May 1, 2013galilmcCWE-20EPSS 2.79%

Overview

CVE-2013-0699 is a high-severity vulnerability affecting galilmc rio-47100_plc. It was published on May 1, 2013 and has a CVSS 2.0 base score of 7.1 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.1, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

The Galil RIO-47100 Pocket PLC allows remote attackers to cause a denial of service via a session that includes "repeated requests."

Remediation

Check the references section for vendor advisories and patches from galilmc. Update rio-47100_plc to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2013-0699?

CVE-2013-0699 is a high-severity vulnerability affecting galilmc rio-47100_plc. It was published on May 1, 2013 and has a CVSS 2.0 base score of 7.1 (HIGH).

How severe is CVE-2013-0699?

This vulnerability has a CVSS 2.0 base score of 7.1, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2013-0699?

Check the references section for vendor advisories and patches from galilmc. Update rio-47100_plc to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2013-0699?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2013-0699 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2013

View all