CVE-2024-44809: camera-pi · Improper Input Validation
Affects camera-piSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubrecantha/camera-pipkg:github/recantha/camera-piOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately restrict network access to the Pi Camera application, ensuring it is not exposed to untrusted or public networks. Use firewalls or network segmentation to limit access to trusted management networks only. 2. Implement web application firewalls (WAFs) or intrusion prevention systems (IPS) with custom rules to detect and block malicious payloads targeting the "position" GET parameter in tilt.php. 3. Apply strict input validation and sanitization on the "position" parameter by whitelisting acceptable values and rejecting any input containing special characters or command sequences. 4. If possible, disable or remove the tilt.php script or the vulnerable functionality until a vendor patch is available. 5. Monitor logs for suspicious requests targeting the tilt.php endpoint, especially those containing unusual characters or command injection patterns. 6. Follow vendor communications closely and apply official patches or updates as soon as they are released. 7. Consider deploying application-layer authentication or VPN access to restrict usage to authorized users only. 8. Conduct regular security assessments and penetration tests on IoT and embedded devices to identify similar input validation flaws. 9. Educate system administrators about the risks of exposing camera control interfaces to untrusted networks and enforce secure deployment guidelines.
Description
A remote code execution (RCE) vulnerability exists in the Pi Camera project, version 1.0, maintained by RECANTHA. The issue arises from improper sanitization of user input passed to the "position" GET parameter in the tilt.php script. An attacker can exploit this by sending crafted input data that includes malicious command sequences, allowing arbitrary commands to be executed on the server with the privileges of the web server user. This vulnerability is exploitable remotely and poses significant risk if the application is exposed to untrusted networks.