Security readout for executives and security teams
Plain-English summary
VegaBird Vooki 5.2.9 is reported vulnerable to DLL hijacking. If an attacker can place a malicious DLL beside Vooki.exe, it may run code with the application’s privileges and support persistence. The record rates this critical, but public details are sparse and affected-product metadata is incomplete.
Executive priority
Prioritize validation this cycle if Vooki is deployed. The potential impact is high, but urgency depends on whether attackers can write into Vooki directories and whether the product is business-critical or broadly installed.
Technical view
CVE-2024-45874 describes arbitrary code execution via DLL search/order hijacking in Vooki 5.2.9. The CVE lists CVSS 9.8 with network, low-complexity, no-privilege, no-user-interaction metrics. That conflicts somewhat with the described need to place a DLL in the Vooki.exe directory, so validate local exposure carefully.
Likely exposure
Organizations running VegaBird Vooki 5.2.9 are the known exposed population from the provided sources. Exposure is higher where users or attackers can write to the Vooki installation directory, software distribution paths, or shared locations containing Vooki.exe.
Exploitation context
The source bundle references a Packet Storm entry via Sploitus, indicating public exploit-oriented material exists. CISA KEV is false in the bundle, and no cited source confirms active exploitation in the wild.
Researcher notes
The CVE affected-product fields show n/a, while the description names VegaBird Vooki 5.2.9. Treat the CVSS vector cautiously because DLL placement usually implies a prerequisite write path. No official patch information is present in the provided sources.
Mitigation direction
- Check VegaBird guidance for fixed versions or official mitigation.
- Upgrade or replace Vooki 5.2.9 if vendor guidance identifies a safe version.
- Remove write access for non-administrators on Vooki installation directories.
- Use application control to restrict unsigned or unexpected DLL loading.
- Monitor for unexpected DLLs near Vooki.exe.
- Run Vooki with least necessary privileges.
Validation and detection
- Inventory endpoints and servers for VegaBird Vooki 5.2.9.
- Locate Vooki.exe paths and review directory permissions.
- Check whether standard users can write beside Vooki.exe.
- Review EDR alerts for suspicious DLL loads by Vooki.exe.
- Compare installed files against a trusted software baseline.
- Track CVE and vendor pages for remediation updates.
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-45874 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:181913CVE 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.