LiveActive security incident?Get immediate response
CVE Record

CVE-2023-37733: An arbitrary file upload vulnerability in tduck-platform v4.0 allows attackers to execute arbitrary code vi...

An arbitrary file upload vulnerability in tduck-platform v4.0 allows attackers to execute arbitrary code via a crafted HTML file.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-37733 concerns tduck-platform v4.0. The CVE description says an arbitrary file upload issue can allow arbitrary code execution through a crafted HTML file. That is a serious impact, but the public bundle does not provide CVSS scoring, affected CPEs, a confirmed patch, or active exploitation evidence.

Executive priority

Treat this as a high-priority exposure review if tduck-platform v4.0 is in use. Arbitrary code execution can affect system integrity, but urgency depends on whether the upload path is reachable and whether vendor remediation exists.

Technical view

The available record describes arbitrary file upload in tduck-platform v4.0 leading to arbitrary code execution via crafted HTML. No CWE, CVSS vector, vulnerable endpoint, authentication requirement, patch commit, or fixed version is provided in the supplied sources.

Likely exposure

Exposure appears limited to organizations running tduck-platform v4.0, especially deployments where untrusted users can upload or submit HTML files. The supplied affected-products metadata is incomplete, so version scope beyond v4.0 is not established.

Exploitation context

The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. Public references include the project repository and a GitHub issue, but the bundle does not include exploit maturity details.

Researcher notes

Evidence is sparse. The CVE names tduck-platform v4.0 and code execution via crafted HTML, but omits endpoint details, prerequisites, CVSS, CWE, and remediation. Avoid assuming broader affected versions or confirmed exploitation without additional vendor or advisory data.

Mitigation direction

  • Identify any deployed tduck-platform v4.0 instances.
  • Review the linked GitHub issue and repository for vendor guidance.
  • Restrict access to upload functionality where feasible.
  • Limit accepted file types and block untrusted HTML uploads.
  • Monitor application logs for suspicious upload activity.

Validation and detection

  • Confirm whether tduck-platform v4.0 is present in asset inventory.
  • Review deployment configuration for user-accessible upload features.
  • Check repository and issue references for fixed-version guidance.
  • Inspect recent uploads for unexpected HTML content.
  • Verify upload controls reject unauthorized or unsafe file types.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

Execution 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 lookup
description · low confidence lookup

File 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 lookup
cve · low confidence lookup

CVE-2023-37733 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.