Command execution via unsanitized autoUpTime parameter
Published Jan 27, 2023 · Updated Mar 28, 2025
OS command injection in Phicomm K2 firmware 22.6.534.263 allows local users to execute arbitrary commands via autoUpTime. The automatic upgrade function passes the attacker-controlled autoUpTime value into an operating-system command without neutralizing command syntax. Exploitation requires low-privilege local access and can read or alter data and interrupt the router under the firmware process's authority.
Summary
What happened
OS command injection in Phicomm K2 firmware 22.6.534.263 allows local users to execute arbitrary commands via autoUpTime. The automatic upgrade function passes the attacker-controlled autoUpTime value into an operating-system command without neutralizing command syntax. Exploitation requires low-privilege local access and can read or alter data and interrupt the router under the firmware process's authority.
The record
- CVE
- CVE-2022-48070
- Published
- Jan 27, 2023
- Updated
- Mar 28, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-78, T1059
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 27, 2023CVE publishedPublication date reported by the CVE source.
- Mar 28, 2025Record 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
No public exploit references are available in this record.
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