Security readout for executives and security teams
Plain-English summary
CVE-2024-51366 describes a critical arbitrary file upload issue in OmegaT v6.0.1. The CVE says a crafted .conf file can lead to arbitrary code execution. Business urgency is high for organizations using OmegaT, but the public record does not identify a vendor patch or confirmed active exploitation.
Executive priority
Treat as urgent for environments using OmegaT v6.0.1, especially on workstations handling external translation projects. Prioritize discovery and vendor-guidance review before broad remediation decisions.
Technical view
The CVE maps to CWE-434 and is scored CVSS 3.1 9.8 with network attack vector, low complexity, no privileges, and no user interaction. The described vulnerable area is the \Roaming\Omega component in OmegaT v6.0.1. A public PoC repository is referenced, but the CVE affected-product metadata is incomplete.
Likely exposure
Exposure is most likely where OmegaT v6.0.1 is installed and processes configuration files or related project/user data from untrusted sources. The CVE record’s affected vendor/product fields are listed as n/a, so inventory validation is important.
Exploitation context
The CVE references a public GitHub PoC repository, indicating public technical details exist. CISA KEV status is false in the supplied bundle, and no cited source confirms active exploitation in the wild.
Researcher notes
The main uncertainty is product metadata quality: the CVE affected fields show n/a while the description names OmegaT v6.0.1. Patch status and active exploitation are not established in the supplied sources.
Mitigation direction
- Identify and prioritize OmegaT v6.0.1 installations.
- Check OmegaT project guidance for patched versions or official mitigations.
- Restrict handling of untrusted .conf files until vendor guidance is confirmed.
- Limit write access to OmegaT user configuration directories.
- Monitor endpoints for unexpected OmegaT configuration changes or child processes.
Validation and detection
- Search software inventory for OmegaT v6.0.1.
- Confirm whether OmegaT uses the \Roaming\Omega path on affected endpoints.
- Review file monitoring for newly introduced or modified .conf files.
- Check vendor site and CVE updates for remediation details.
- Assess endpoint controls that restrict script or binary execution from user paths.
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-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection 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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-51366 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://github.com/Gelcon/PoCofOmegaTV6_0_1CVE reference, mitre
- https://omegat.org/CVE 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.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.