Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2016-2309

7.2 · HIGH

iRZ RUH2 before 2b does not validate firmware patches, which allows remote authenticated users to modify data or cause a denial of service via unspecified vectors.

Published May 30, 2016CWE-345EPSS 0.68%

Overview

CVE-2016-2309 is a high-severity vulnerability. It was published on May 30, 2016 and has a CVSS 3.0 base score of 7.2 (HIGH).

This vulnerability has a CVSS 3.0 base score of 7.2, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

iRZ RUH2 before 2b does not validate firmware patches, which allows remote authenticated users to modify data or cause a denial of service via unspecified vectors.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. 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.

References

Refics-cert.us-cert.gov/advisories/ICSA-16-138-01Refics-cert.us-cert.gov/advisories/ICSA-16-138-01

How CyberStrike helps

Frequently asked questions

What is CVE-2016-2309?

CVE-2016-2309 is a high-severity vulnerability. It was published on May 30, 2016 and has a CVSS 3.0 base score of 7.2 (HIGH).

How severe is CVE-2016-2309?

This vulnerability has a CVSS 3.0 base score of 7.2, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2016-2309?

Check the references section for vendor advisories, patches, and mitigation guidance. 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-2016-2309?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-2309 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 2016

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999