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-34320 Overview
CVE-2024-34320 is a broken access control vulnerability in ProPhoenix Law RMS version v2022.2403.3.101. The Records Management System (RMS) exposes sensitive API endpoints without enforcing proper authorization checks. Unauthenticated attackers reaching the application over the network can invoke protected endpoints and interact with law enforcement data. The flaw is tracked under CWE-284: Improper Access Control and affects a platform used by police agencies to manage case records, evidence, and investigative data.
Critical Impact
Remote attackers can access sensitive law enforcement API endpoints without authentication, enabling disclosure, modification, or destruction of case data.
Affected Products
- ProPhoenix Law RMS v2022.2403.3.101
Discovery Timeline
- 2026-10-13 - CVE-2024-34320 published to NVD
- 2026-10-14 - Last updated in NVD database
Technical Details for CVE-2024-34320
Vulnerability Analysis
ProPhoenix Law RMS is a Records Management System used by law enforcement agencies to store case, incident, and evidence records. The vulnerability resides in the application's REST API layer, where several endpoints classified as sensitive do not validate the caller's authentication state or role. A remote attacker only needs network reachability to the RMS web interface to invoke these endpoints.
The impact spans confidentiality, integrity, and availability of records. Attackers can retrieve investigative records, modify case data, or disrupt operational data used by officers in the field. Because the issue is a control-plane flaw rather than a memory bug, exploitation requires no custom tooling beyond an HTTP client.
No public exploit code has been released, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Related research into the ProPhoenix Law RMS product line is documented in the CVE-2024-34323 authentication bypass analysis.
Root Cause
The root cause is missing or improperly enforced authorization logic on API endpoints [CWE-284]. Server-side handlers trust the client to call only endpoints appropriate for its session rather than validating session identity and role on every request. Function-level access control is absent on endpoints that return or mutate sensitive data.
Attack Vector
The attack vector is network-based and requires no authentication or user interaction. An attacker identifies the ProPhoenix Law RMS application, enumerates its API endpoints, and issues direct HTTP requests to protected routes. The server processes the requests and returns data or applies modifications without verifying privileges. Successful exploitation yields read and write access to records normally restricted to authenticated law enforcement personnel.
No verified proof-of-concept code is available. Refer to the vendor product page and third-party research for additional context.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2024-34320
Indicators of Compromise
- Unauthenticated HTTP requests to ProPhoenix Law RMS API endpoints returning HTTP 200 responses with sensitive payloads.
- API access patterns originating from IP addresses outside the known law enforcement network ranges.
- Spikes in GET or POST volume against record, case, or evidence endpoints without preceding authentication traffic.
Detection Strategies
- Review web server and application logs for requests to sensitive API routes that lack a valid session cookie or bearer token.
- Deploy a web application firewall (WAF) rule that denies unauthenticated requests to RMS API paths and alerts on violations.
- Correlate RMS API access with authentication events to identify requests that bypass the login flow.
Monitoring Recommendations
- Forward RMS application and reverse proxy logs to a centralized log platform for retention and correlation.
- Alert on anomalous data-export volumes, bulk record enumeration, and off-hours API usage.
- Monitor outbound connections from the RMS server for signs of data staging or exfiltration.
How to Mitigate CVE-2024-34320
Immediate Actions Required
- Restrict network access to the ProPhoenix Law RMS application to trusted law enforcement networks using firewall ACLs or VPN gating.
- Contact ProPhoenix for a fixed build and remediation guidance for v2022.2403.3.101.
- Audit application and API logs for prior unauthorized access to sensitive endpoints.
Patch Information
No public patch advisory is referenced in the NVD entry at the time of publication. Operators running ProPhoenix Law RMS v2022.2403.3.101 should contact the vendor through the ProPhoenix Law RMS product page to obtain a remediated release and confirm that server-side authorization checks are enforced on all sensitive API endpoints.
Workarounds
- Place the RMS application behind a reverse proxy or VPN that enforces authentication before requests reach the API layer.
- Apply WAF rules that block unauthenticated access to /api/ paths and sensitive record endpoints.
- Segment the RMS server from general-purpose networks and limit administrative access to a jump host.
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

