Stack-based Buffer Overflow vulnerability in cachekey plugin of Apache Traffic Server. This issue affects Apache Traffic Server 7.0.0 to 7.1.12, 8.0.0 to 8.1.1, 9.0.0 to 9.0.1.
Weakness
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Traffic_server |
Apache |
7.0.0 (including) |
7.1.12 (including) |
| Traffic_server |
Apache |
8.0.0 (including) |
8.1.1 (including) |
| Traffic_server |
Apache |
9.0.0 (including) |
9.0.1 (including) |
| Trafficserver |
Ubuntu |
bionic |
* |
| Trafficserver |
Ubuntu |
devel |
* |
| Trafficserver |
Ubuntu |
esm-apps/focal |
* |
| Trafficserver |
Ubuntu |
esm-apps/jammy |
* |
| Trafficserver |
Ubuntu |
esm-apps/noble |
* |
| Trafficserver |
Ubuntu |
focal |
* |
| Trafficserver |
Ubuntu |
groovy |
* |
| Trafficserver |
Ubuntu |
hirsute |
* |
| Trafficserver |
Ubuntu |
impish |
* |
| Trafficserver |
Ubuntu |
jammy |
* |
| Trafficserver |
Ubuntu |
kinetic |
* |
| Trafficserver |
Ubuntu |
lunar |
* |
| Trafficserver |
Ubuntu |
mantic |
* |
| Trafficserver |
Ubuntu |
noble |
* |
| Trafficserver |
Ubuntu |
oracular |
* |
| Trafficserver |
Ubuntu |
plucky |
* |
| Trafficserver |
Ubuntu |
questing |
* |
| Trafficserver |
Ubuntu |
trusty |
* |
| Trafficserver |
Ubuntu |
upstream |
* |
| Trafficserver |
Ubuntu |
xenial |
* |
Potential Mitigations
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
- D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
- Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
- For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].
References