Skip to main content
VulnerabilityPublished Updated

CVE-2023-48834: Car Rental · Uncontrolled Resource Consumption

Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 64% 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:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Dec 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

AI-suggested

To mitigate this vulnerability effectively, European organizations should implement strict rate limiting and throttling controls at multiple layers. Specifically, deploying web application firewalls (WAFs) with custom rules to detect and limit the frequency of requests to the pjActionAjaxSend endpoint can prevent resource exhaustion attacks. Network-level protections such as intrusion prevention systems (IPS) and DDoS mitigation services should be configured to identify and block abnormal traffic patterns targeting the vulnerable function. Application-level mitigations include adding or enhancing rate limiting logic within the Car Rental v3.0 application code to restrict the number of requests per IP address or user session within a defined time window. Organizations should also conduct thorough logging and monitoring of access to the vulnerable endpoint to detect early signs of abuse. If possible, isolating or segmenting the vulnerable service from critical infrastructure can reduce the blast radius of an attack. Until an official patch or update is released, organizations should consider temporarily disabling or restricting access to the vulnerable functionality if feasible. Finally, maintaining an incident response plan that includes procedures for handling DoS attacks will improve preparedness and response times.

Description

A lack of rate limiting in pjActionAjaxSend in Car Rental v3.0 allows attackers to cause resource exhaustion.

References

Community reviews

Loading reviews…