rabidhamster vulnerabilities

Products

• r2extreme 3
• r2 1
• R4 Embedded Server 1

Latest rabidhamster CVEs

Newest publication first

1. CVE-2012-10058 RabidHamster R4 Log Entry sprintf() Buffer Overflow

   Published 2025-08-13

   Critical·CVSS 10.0 EPSS 2.2% Framework module

   RabidHamster R4 v1.25 contains a stack-based buffer overflow vulnerability due to unsafe use of sprintf() when logging malformed HTTP requests. A remote attacker can exploit this flaw by sending a specially crafted URI, resulting in arbitrary code execution under the context of t...

2. CVE-2012-1223 RabidHamster R2/Extreme 1.65 and earlier uses a small search space of values for the PIN number, which allows remote attackers to obtain the PIN number via a brute force attack.

   Published 2012-02-21

   Medium·CVSS 5.0 EPSS 1.4%

   RabidHamster R2/Extreme 1.65 and earlier uses a small search space of values for the PIN number, which allows remote attackers to obtain the PIN number via a brute force attack.

3. CVE-2012-1222 Stack-based buffer overflow in RabidHamster R2/Extreme 1.65 and earlier allows remote authenticated users to execute arbitrary code via a long string to TCP port 23.

   Published 2012-02-21

   High·CVSS 8.5 EPSS 3.8%

   Stack-based buffer overflow in RabidHamster R2/Extreme 1.65 and earlier allows remote authenticated users to execute arbitrary code via a long string to TCP port 23.

4. CVE-2012-1221 Directory traversal vulnerability in the telnet server in RabidHamster R2/Extreme 1.65 and earlier allows remote attackers to read arbitrary files via a .. (dot dot) in the File command.

   Published 2012-02-21

   Medium·CVSS 5.0 EPSS 2.9% Public exploit

   Directory traversal vulnerability in the telnet server in RabidHamster R2/Extreme 1.65 and earlier allows remote attackers to read arbitrary files via a .. (dot dot) in the File command.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.