Security readout for executives and security teams
Plain-English summary
CVE-2023-3049 is a critical file-upload flaw in TMT Lockcell before version 15. An unauthenticated network attacker could upload a dangerous file type and achieve command injection, potentially taking control of the affected system. The sources do not show confirmed active exploitation, but public technical/exploit-related material is referenced.
Executive priority
Treat as an immediate remediation item for any Lockcell deployment. The vulnerability is remotely reachable, requires no authentication, and can enable full system compromise. Business urgency depends on whether Lockcell is deployed and exposed, but affected systems should not remain unremediated.
Technical view
The CVE describes CWE-434: unrestricted upload of a file with dangerous type in TMT Lockcell before 15, leading to command injection. CVSS is 9.8 with network attack vector, low complexity, no privileges, and no user interaction. Impact is high for confidentiality, integrity, and availability.
Likely exposure
Organizations running TMT Lockcell versions before 15 are the stated exposed population. Internet-facing deployments or systems accepting file uploads would carry the highest practical risk. The provided CPE data is incomplete, so asset discovery may require product-specific inventory checks.
Exploitation context
CISA KEV status is false in the provided bundle, and no cited source confirms active exploitation. One reference is tagged as exploit and technical description, indicating public offensive or proof-of-concept context may exist. Treat exposure as urgent even without confirmed in-the-wild activity.
Researcher notes
The record is concise and lacks detailed affected-version metadata beyond “before 15.” One government link is marked broken in the bundle. Avoid assuming exploitation beyond the public exploit-tagged reference. Focus validation on version confirmation, exposure, and evidence of suspicious upload activity.
Mitigation direction
- Identify all TMT Lockcell deployments and record installed versions.
- Prioritize upgrading Lockcell instances before version 15 to version 15 or later.
- If upgrade timing is unclear, check current TMT or government advisory guidance.
- Restrict external access to Lockcell until remediation is complete.
- Review upload handling controls and monitoring around Lockcell systems.
Validation and detection
- Confirm whether any Lockcell instance is running a version before 15.
- Verify upgraded systems report version 15 or later.
- Check exposure of Lockcell interfaces from the internet and untrusted networks.
- Review logs for suspicious uploads or command-execution indicators.
- Document exceptions where version or vendor guidance cannot be verified.
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-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-2023-3049 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.9TR-CERTVulnerability 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://www.usom.gov.tr/bildirim/tr-23-0345CVE reference, TR-CERT · government-resource, broken-link
- https://fordefence.com/cve-2023-3049-unrestricted-upload-of-file-with-dangerous-type-vulnerability-allows-command-injection/CVE reference, TR-CERT · exploit, technical-description
- https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-23-0345CVE reference, TR-CERT · government-resource
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.