Axessh 4.2 Local Stack-based Buffer Overflow via Log File Name
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Labf | Axessh | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Labf | Axessh |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.157% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Labf
Labf axessh |
|
| Vendors & Products |
Labf
Labf axessh |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Axessh 4.2 contains a stack-based buffer overflow vulnerability in the log file name field that allows local attackers to execute arbitrary code by supplying an excessively long filename. Attackers can overflow the buffer at offset 214 bytes to overwrite the instruction pointer and execute shellcode with system privileges. | |
| Title | Axessh 4.2 Local Stack-based Buffer Overflow via Log File Name | |
| Weaknesses | CWE-787 | |
| References |
| |
| Metrics |
cvssV3_1
|