Skip to main content
Vulnerability Database/CVE-2024-34324

CVE-2024-34324: ProPhoenix Law RMS Session Hijacking Flaw

CVE-2024-34324 is a session hijacking vulnerability in ProPhoenix Law RMS v2022.2403.3.101 that allows attackers to bypass authentication by injecting a crafted string into the ASP.NET_SessionId cookie. This article covers technical details, affected versions, security impact, and mitigation strategies.

Published:

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-34324 Overview

CVE-2024-34324 is a session hijacking vulnerability affecting ProPhoenix Law RMS version 2022.2403.3.101. Attackers can hijack authenticated sessions by injecting a crafted 24-character string into the ASP.NET_SessionId cookie. The flaw maps to CWE-384: Session Fixation and allows network-based exploitation without authentication or user interaction. ProPhoenix Law RMS is a records management system used by law enforcement agencies, so successful exploitation exposes sensitive case data and investigative records.

Critical Impact

Unauthenticated remote attackers can hijack valid user sessions and gain access to law enforcement records by manipulating a predictable session cookie value.

Affected Products

  • ProPhoenix Law RMS v2022.2403.3.101
  • Earlier builds in the ProPhoenix Law RMS 2022 branch that share the same session handling logic
  • Deployments exposing the web interface over the network without additional session hardening

Discovery Timeline

  • 2026-10-13 - CVE-2024-34324 published to the National Vulnerability Database
  • 2026-10-14 - Last updated in NVD database

Technical Details for CVE-2024-34324

Vulnerability Analysis

The vulnerability resides in how ProPhoenix Law RMS validates the ASP.NET_SessionId cookie. The application accepts any 24-character string that matches the expected cookie format as a legitimate session identifier. This behavior allows an attacker to inject a crafted value and bind it to an authenticated user's session, enabling classic session fixation and hijacking attacks.

Because the attack is executed over the network against the web application, no credentials or user interaction are required beyond the ability to influence or guess a target's session cookie. The confidentiality and integrity impact is high, as law enforcement records can be read and modified under the hijacked user's privileges.

Root Cause

The root cause is weak session identifier handling associated with [CWE-384]. The application does not regenerate the ASP.NET_SessionId on authentication state changes and does not sufficiently bind the cookie value to additional server-side session context such as client fingerprint or authentication token. A fixed or attacker-chosen 24-character value is treated as a valid session identifier.

Attack Vector

An attacker crafts a 24-character string conforming to the ASP.NET_SessionId format and delivers it to a victim through cross-site scripting, a malicious link, or a shared network path. When the victim authenticates to ProPhoenix Law RMS using that session identifier, the attacker reuses the same cookie value in their own browser to assume the victim's authenticated session. See the related analysis of CVE-2024-34323 for context on related ProPhoenix Law RMS issues.

No verified exploit code is published for CVE-2024-34324. The vulnerability mechanism is described in prose because no sanitized proof-of-concept is available in authoritative sources.

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 Attacks

Detection Methods for CVE-2024-34324

Indicators of Compromise

  • Multiple distinct source IP addresses presenting the same ASP.NET_SessionId cookie value within short time windows
  • Authenticated sessions originating from geolocations or user agents inconsistent with the account's baseline
  • ASP.NET_SessionId cookie values that remain static across authentication events for the same user
  • Access to ProPhoenix Law RMS records from endpoints not enrolled in the agency's device inventory

Detection Strategies

  • Correlate web server access logs on session identifiers to identify cookies used from more than one client simultaneously
  • Alert on session identifiers that persist across logout and re-authentication events, indicating missing session regeneration
  • Monitor for unusual record access patterns such as bulk case reads or exports following a session cookie change

Monitoring Recommendations

  • Forward IIS or application logs for the ProPhoenix Law RMS host to a central SIEM for session cookie analytics
  • Enable web application firewall logging of Cookie headers and tag any requests presenting externally supplied ASP.NET_SessionId values
  • Track administrative and investigative queries against RMS records and baseline them per user for anomaly detection

How to Mitigate CVE-2024-34324

Immediate Actions Required

  • Contact ProPhoenix for a fixed build and apply it as soon as it is available for version 2022.2403.3.101
  • Restrict access to the Law RMS web interface to trusted agency networks or a VPN until patched
  • Force logout of all active sessions and require users to re-authenticate after any protective change
  • Enforce HTTPS end to end and set the ASP.NET_SessionId cookie with Secure, HttpOnly, and SameSite=Strict attributes

Patch Information

No public patch identifier is listed in the NVD entry for CVE-2024-34324 at the time of publication. Agencies running ProPhoenix Law RMS should contact the vendor directly through the ProPhoenix Law RMS product page to confirm the fixed build and remediation guidance.

Workarounds

  • Place the application behind a reverse proxy or web application firewall that rewrites or validates ASP.NET_SessionId cookies
  • Reduce session lifetime and idle timeout values to limit the window of exploitation for hijacked identifiers
  • Require multi-factor authentication at the identity provider so that a stolen session alone cannot grant persistent access
  • Audit and rotate any shared or long-lived service accounts that interact with ProPhoenix Law RMS
bash
# Example IIS configuration to harden ASP.NET session cookies
# web.config snippet - review with vendor before deploying
<system.web>
  <sessionState cookieless="UseCookies" regenerateExpiredSessionId="true" timeout="15" />
  <httpCookies httpOnlyCookies="true" requireSSL="true" sameSite="Strict" />
</system.web>

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.