Security readout for executives and security teams
Plain-English summary
Yaazhini 2.0.2 is reported to load a malicious DLL placed beside Yaazhini.exe, letting an attacker run code as the application. That can support compromise or persistence. The record rates it critical, but public details are sparse and the affected product metadata is incomplete.
Executive priority
Prioritize this as urgent where Yaazhini 2.0.2 is installed, especially on shared or high-value systems. The rating is critical, but evidence is incomplete, so decisions should be based on confirmed presence and vendor guidance.
Technical view
The CVE describes DLL hijacking in VegaBird Yaazhini 2.0.2. A crafted DLL in the same directory as Yaazhini.exe may be loaded by the process, enabling arbitrary code execution and persistence. The CVSS 3.1 score is 9.8, though the described placement requirement should be validated against vendor details.
Likely exposure
Exposure appears limited to environments running VegaBird Yaazhini 2.0.2. The CVE affected-product fields list n/a, so asset teams should confirm installations by software inventory rather than relying only on CPE matching.
Exploitation context
A public Sploitus/PacketStorm reference is listed. The source bundle does not show CISA KEV listing or cite active exploitation. Treat the public reference as increased research and detection urgency, not proof of in-the-wild exploitation.
Researcher notes
The record has a high CVSS score and public exploit reference, but sparse technical detail. The affected vendor/product fields are n/a despite the description naming VegaBird Yaazhini 2.0.2. Validate the DLL placement prerequisite and privilege context before assuming remote unauthenticated exploitability.
Mitigation direction
- Check VegaBird/vendor guidance for patched Yaazhini builds or official mitigations.
- Restrict write access to Yaazhini installation and execution directories.
- Remove unexpected DLLs located alongside Yaazhini.exe after validation.
- Prioritize upgrade, isolation, or removal where Yaazhini 2.0.2 is business-critical.
- Monitor endpoint detections for suspicious DLL loading by Yaazhini.exe.
Validation and detection
- Inventory endpoints and servers for VegaBird Yaazhini 2.0.2.
- Confirm Yaazhini.exe installation paths and directory write permissions.
- Review the application directory for unexpected or recently added DLL files.
- Check EDR/process telemetry for unusual child processes or DLL loads.
- Track CVE and vendor records for corrected affected-product and fix data.
Public sources used
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-45873 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
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:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://sploitus.com/exploit?id=PACKETSTORM:181912CVE reference, mitre
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.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.