CVE-2019-25590 | Labf Axessh 4.2 Configuration log file name assumed-immutable data is stored in writable memory (Exploit 46858 / EDB-46858)

VDB-352443 · CVE-2019-25590 · EXPLOIT 46858 LABF AXESSH 4.2 CONFIGURATION LOG FILE NAME ASSUMED-IMMUTABLE DATA IS STORED IN WRITABLE MEMORY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.6 $0-$5k 2.20+ Summaryinfo 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. Detailsinfo 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 vulnerability database at Exploit-DB (46858). Productinfo Vendor Labf Name Axessh Version 4.2 CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 4.7 VulDB 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): 🔒 CVSSv2info 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: 🔍 Exploitinginfo Class: Assumed-immutable data is stored in writable memory CWE: CWE-1282 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: No Availability: 🔒 Access: Public Status: Proof-of-Concept Download: 🔒 Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Exploit-DB: 🔒 Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 03/22/2026 Advisory disclosed 03/22/2026 +0 days CVE reserved 03/22/2026 +0 days VulDB entry created 03/22/2026 +0 days VulDB entry last update Sourcesinfo Advisory: 46858 Researcher: Victor Mondragón Status: Not defined CVE: CVE-2019-25590 (🔒) GCVE (CVE): GCVE-0-2019-25590 GCVE (VulDB): GCVE-100-352443 scip Labs: https://www.scip.ch/en/?labs.20161013 Entryinfo Created: 03/22/2026 15:51 Changes: 03/22/2026 15:51 (80) Complete: 🔍 Cache ID: 99:0FB:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸