Labf Axessh 4.2 Configuration log file name assumed-immutable data is stored in writable memory
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Labf Axessh 4.2. It has been rated as problematic. This vulnerability affects unknown code of the component Configuration Handler. Performing a manipulation of the argument log file name results in assumed-immutable data is stored in writable memory. This vulnerability was named CVE-2019-25590. The attack needs to be approached locally. In addition, an exploit is available.
Details
A vulnerability, which was classified as problematic, was found in Labf Axessh 4.2. This affects an unknown function of the component Configuration Handler. The manipulation of the argument log file name with an unknown input leads to a assumed-immutable data is stored in writable memory vulnerability. CWE is classifying the issue as CWE-1282. Immutable data, such as a first-stage bootloader, device identifiers, and "write-once" configuration settings are stored in writable memory that can be re-programmed or updated in the field. This is going to have an impact on availability. The summary by CVE is:
Axessh 4.2 contains a denial of service vulnerability in the logging configuration that allows local attackers to crash the application by supplying an excessively long string in the log file name field. Attackers can enable session logging, paste a buffer of 500 or more characters into the log file name parameter, and trigger a crash when establishing a telnet connection.
The weakness was presented by Victor Mondragón as 46858. It is possible to read the advisory at exploit-db.com. This vulnerability is uniquely identified as CVE-2019-25590 since 03/22/2026. The exploitability is told to be easy. Attacking locally is a requirement. Technical details and a public exploit are known.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Exploit-DB (46858) and CNNVD (CNNVD-202603-4152). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.6
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.2
CNA Vector (VulnCheck): 🔒
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: Assumed-immutable data is stored in writable memoryCWE: CWE-1282
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔒
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/22/2026 Advisory disclosed03/22/2026 CVE reserved
03/22/2026 VulDB entry created
03/23/2026 VulDB entry last update
Sources
Advisory: 46858Researcher: Victor Mondragón
Status: Not defined
CVE: CVE-2019-25590 (🔒)
GCVE (CVE): GCVE-0-2019-25590
GCVE (VulDB): GCVE-100-352443
CNNVD: CNNVD-202603-4152 - LabF Axessh 安全漏洞
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/22/2026 15:51Updated: 03/23/2026 17:29
Changes: 03/22/2026 15:51 (80), 03/23/2026 17:29 (6)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.