Security readout for executives and security teams
CVE-2019-25590 affects LabF Axessh 4.2. A local attacker can crash the application through an overly long log file name in the logging configuration. This is an availability issue for the Axessh client, not evidence of system takeover. Public exploit information exists, but the provided sources do not show active exploitation. Exposure is limited to environments running LabF Axessh 4.2, especially shared workstations or systems where untrusted local users can access the client configuration. Network-only exposure is not supported by the provided sources. Treat as a moderate operational risk. Prioritize if Axessh 4.2 is used on shared systems, critical admin workstations, or support environments. This is less urgent than remotely exploitable server vulnerabilities, but public exploit availability increases the need to inventory and retire or update exposed installations. Mitigation focus: Inventory systems for LabF Axessh 4.2 installations.; Check LabF or trusted vendor guidance for an updated or supported version.; Remove Axessh 4.2 where it is no longer required..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1282: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2019-25590 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
6.9MediumVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-46858CVE reference · exploit
- VulnCheck Advisory: Axessh 4.2 Denial of Service via Log File NameCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Assumed-Immutable Data is Stored in Writable Memory
Assumed-Immutable Data is Stored in Writable Memory represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.