Security readout for executives and security teams
AutoYaST in SUSE Linux Enterprise Server 12 and 15 could automatically import GPG keys without verifying them when deprecated image-creation functionality was used. In a man-in-the-middle position, an attacker could influence builds, but the CVSS vector indicates high attack complexity and limited integrity and availability impact. Exposure is most likely on SUSE build or provisioning systems that create images with AutoYaST and still use the deprecated functionality. Ordinary deployed SLES systems are not clearly exposed unless they run the vulnerable autoyast2 workflow. Treat this as a moderate supply-chain and provisioning risk, not a broad production-server emergency. Prioritize teams that build SUSE images or manage automated provisioning, because compromise there could affect downstream systems. Mitigation focus: Inventory SLES 12 and SLES 15 systems with autoyast2 installed.; Update autoyast2 according to SUSE or openSUSE advisory guidance.; Stop using the deprecated AutoYaST functionality where feasible..
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-345: 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-18905 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
- 4.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
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:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L2.22.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.8MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://bugzilla.suse.com/show_bug.cgi?id=1140711CVE reference · x_refsource_CONFIRM
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.
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.