Security readout for executives and security teams
Plain-English summary
UpTrain 0.7.1 and earlier can let an authenticated user run arbitrary code through the project-creation function. Successful abuse could compromise the confidentiality, integrity, and availability of the UpTrain host environment, commonly its Docker container. No patch was known when the advisory was published.
Executive priority
Treat reachable affected deployments as a high-priority containment issue. Identify owners immediately, restrict access, and strengthen isolation while monitoring vendor guidance. Escalate instances containing sensitive data or connected to privileged internal services.
Technical view
The `/create_project` endpoint improperly handles the `checks` and `metadata` parameters, enabling code injection classified as CWE-74. Exploitation is network-accessible, low-complexity, requires valid authentication, and needs no user interaction. Code executes with the privileges and isolation of the UpTrain process.
Likely exposure
Exposure exists where UpTrain 0.7.1 or earlier is running and an attacker can reach `/create_project` with valid authentication. Internet accessibility, broadly distributed credentials, weak account controls, or an inadequately isolated container increase practical risk. The supplied sources identify no other affected products.
Exploitation context
The CVSS 4.0 vector records proof-of-concept exploit maturity (`E:P`), but the supplied sources do not establish active exploitation. The CVE is not marked as KEV. Authentication is required, although any authorized user reaching the affected endpoint may potentially exploit it.
Researcher notes
The cited vulnerable code and advisory associate unsafe handling of `checks` and `metadata` with code execution. Assessment should remain non-destructive: establish version, endpoint reachability, authorization scope, process privileges, container boundaries, mounts, secrets, and network adjacency. Patch status requires continued vendor verification.
Mitigation direction
- Check UpTrain vendor guidance regularly because no known patch was available at publication.
- Restrict UpTrain access to trusted users and networks while awaiting an official fix.
- Review and revoke unnecessary UpTrain accounts, credentials, and authentication paths.
- Isolate the UpTrain container and minimize its privileges and access to sensitive systems.
- Consider suspending affected instances when compensating controls cannot adequately restrict access.
Validation and detection
- Inventory all UpTrain deployments and identify versions at or below 0.7.1.
- Confirm whether `/create_project` is reachable and which authenticated users can invoke it.
- Review authentication records for unexpected accounts, access patterns, or credential use.
- Inspect container and host telemetry for unusual processes, files, or outbound connections.
- Verify the service runs with minimal privileges and appropriately restricted mounts and network access.
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-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-27770 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
- High
- CVSS
- 7.4 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
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:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
7.4HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
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://securitylab.github.com/advisories/GHSL-2024-198_GHSL-2024-199_Uptrain/CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/uptrain-ai/uptrain/blob/a31cc14eddcb6c0b0b12cbed15f086d98c441c6f/uptrain/dashboard/backend/app.py#L691C22-L691C36CVE reference, GitHub_M · x_refsource_MISC
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 Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.