Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-12984 Overview
CVE-2024-12984 is an information disclosure vulnerability affecting multiple Amcrest IP camera models, including the IP2M-841B, IP2M-841W, IPC-IP2M-841B, IPC-IP3M-943B, IPC-IP3M-943S, IPC-IP3M-HX2B, and IPC-IPM-721S up to firmware version 20241211. The flaw resides in the /web_caps/webCapsConfig endpoint of the camera's Web Interface. Remote attackers can query this endpoint without authentication to retrieve sensitive device configuration data. The exploit has been publicly disclosed, and the vendor did not respond to coordinated disclosure attempts. The weakness is categorized under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Critical Impact
Unauthenticated remote attackers can retrieve sensitive configuration information from affected Amcrest IP cameras over the network, aiding reconnaissance and follow-on attacks.
Affected Products
- Amcrest IP2M-841B, IP2M-841W, and IPC-IP2M-841B cameras up to firmware 20241211
- Amcrest IPC-IP3M-943B, IPC-IP3M-943S, and IPC-IP3M-HX2B cameras up to firmware 20241211
- Amcrest IPC-IPM-721S cameras up to firmware 20241211
Discovery Timeline
- 2024-12-27 - CVE-2024-12984 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-12984
Vulnerability Analysis
The vulnerability resides in the /web_caps/webCapsConfig resource exposed by the camera's embedded Web Interface. The endpoint returns configuration information without enforcing authentication or authorization checks. An attacker on the network path to the camera can issue a direct HTTP request and receive device configuration data in the response. Because the attack requires no credentials, no user interaction, and only network reachability, exposed cameras on the internet or on flat enterprise LANs are at elevated exposure. The data returned supports fingerprinting, inventory enumeration, and planning of follow-on attacks against the device or network segment.
Root Cause
The root cause is a missing access control check on the /web_caps/webCapsConfig handler within the embedded web server. The handler serves configuration data intended for authenticated administrative use but does not validate session state or verify a privileged role before responding. This design flaw aligns with [CWE-200] and reflects an insecure default in the firmware's web routing layer.
Attack Vector
Exploitation is performed over the network. An attacker crafts an HTTP request to the vulnerable endpoint on the camera's management interface. No authentication header, session cookie, or multi-step precondition is required. The server returns configuration information directly in the HTTP response body. The attack can be automated and scaled across internet-exposed cameras discoverable through standard scanning techniques. See the Netsecfish technical write-up for additional detail. No verified proof-of-concept code is reproduced here.
Detection Methods for CVE-2024-12984
Indicators of Compromise
- Unexpected HTTP GET requests to the URI path /web_caps/webCapsConfig on Amcrest camera management interfaces.
- Outbound HTTP responses from camera devices containing configuration payloads to untrusted source addresses.
- Scanning patterns targeting TCP port 80 or 443 on IP camera subnets, followed by requests to /web_caps/ paths.
Detection Strategies
- Deploy network IDS or web application firewall signatures that alert on HTTP requests containing /web_caps/webCapsConfig to Amcrest device IP ranges.
- Correlate camera access logs with source IP reputation data to flag requests from external or non-management hosts.
- Baseline normal management traffic to Amcrest cameras and alert on anomalous unauthenticated access patterns.
Monitoring Recommendations
- Capture and retain HTTP access logs from camera devices or an upstream reverse proxy for forensic review.
- Monitor firewall and NetFlow telemetry for scanning activity targeting IoT subnets hosting Amcrest cameras.
- Alert on configuration data egress patterns from camera VLANs to the internet or unmanaged network segments.
How to Mitigate CVE-2024-12984
Immediate Actions Required
- Remove affected Amcrest cameras from direct internet exposure and place them behind a VPN or management jump host.
- Restrict access to camera management interfaces using network ACLs that permit only authorized administrative subnets.
- Inventory all Amcrest cameras in the environment and identify devices running firmware at or below 20241211.
- Rotate credentials and review stored configuration data for any secrets that may have been exposed.
Patch Information
At the time of publication, the vendor had not responded to the disclosure, and no official patch is referenced in the public advisory. Monitor the Amcrest support site and the VulDB entry for CVE-2024-12984 for firmware updates addressing the /web_caps/webCapsConfig endpoint.
Workarounds
- Block inbound HTTP and HTTPS traffic to camera management interfaces at the perimeter firewall.
- Segment IoT devices onto a dedicated VLAN with no direct routing to user or server networks.
- Place a reverse proxy in front of camera interfaces that enforces authentication and denies requests to /web_caps/ paths.
- Disable the device's web interface where feasible and manage cameras through a hardened Network Video Recorder (NVR).
# Example iptables rule to restrict camera web interface access to a management subnet
iptables -A FORWARD -s 10.10.50.0/24 -d 192.168.20.0/24 -p tcp --dport 80 -j ACCEPT
iptables -A FORWARD -d 192.168.20.0/24 -p tcp --dport 80 -j DROP
iptables -A FORWARD -d 192.168.20.0/24 -p tcp --dport 443 -j DROP
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

