Unauthenticated code execution via crafted network packets
Published Apr 10, 2022 · Updated Aug 3, 2024
OS command injection in InHand Networks InRouter 900 firmware before 1.0.0.r11700 allows remote attackers to execute code via a crafted packet. The record identifies sub_10F2C as the vulnerable locus but does not disclose which packet field reaches an operating-system command sink. No authentication or user interaction is required, and successful exploitation allows arbitrary command execution on the router.
Summary
What happened
OS command injection in InHand Networks InRouter 900 firmware before 1.0.0.r11700 allows remote attackers to execute code via a crafted packet. The record identifies sub_10F2C as the vulnerable locus but does not disclose which packet field reaches an operating-system command sink. No authentication or user interaction is required, and successful exploitation allows arbitrary command execution on the router.
The record
- CVE
- CVE-2022-27276
- Published
- Apr 10, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-78, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 10, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- InRouter 900 RCE researcher artifactproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo