Apache Traffic Server up to 9.2.10/10.0.5 ESI Plugin memory allocation

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Apache Traffic Server up to 9.2.10/10.0.5. Affected by this vulnerability is an unknown functionality of the component ESI Plugin. This manipulation causes memory allocation. The identification of this vulnerability is CVE-2025-49763. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Apache Traffic Server up to 9.2.10/10.0.5. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component ESI Plugin. The manipulation with an unknown input leads to a memory allocation vulnerability. The CWE definition for the vulnerability is CWE-789. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. As an impact it is known to affect availability. The summary by CVE is:
ESI plugin does not have the limit for maximum inclusion depth, and that allows excessive memory consumption if malicious instructions are inserted. Users can use a new setting for the plugin (--max-inclusion-depth) to limit it. This issue affects Apache Traffic Server: from 10.0.0 through 10.0.5, from 9.0.0 through 9.2.10. Users are recommended to upgrade to version 9.2.11 or 10.0.6, which fixes the issue.
The advisory is shared at seclists.org. This vulnerability is known as CVE-2025-49763. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 240505 (Debian dsa-5948 : trafficserver - security update), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 9.2.11 or 10.0.6 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (240505). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory allocationCWE: CWE-789 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 240505
Nessus Name: Debian dsa-5948 : trafficserver - security update
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Traffic Server 9.2.11/10.0.6
Timeline
06/18/2025 🔍06/18/2025 🔍
06/26/2025 🔍
Sources
Vendor: apache.orgAdvisory: seclists.org
Status: Confirmed
CVE: CVE-2025-49763 (🔍)
GCVE (CVE): GCVE-0-2025-49763
GCVE (VulDB): GCVE-100-312829
Entry
Created: 06/18/2025 09:08Updated: 06/26/2025 19:40
Changes: 06/18/2025 09:08 (52), 06/19/2025 13:45 (1), 06/24/2025 04:35 (1), 06/26/2025 19:40 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.