dbcve.org
TripleplayApplication · Uniguest

CVE-2024-50704

CRITICAL · 10.0 CVSS v3.1 Published 2025-03-04
Fix available
A fix is available. Upgrade to 24.1.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unauthenticated remote code execution vulnerability in Uniguest Tripleplay before 24.2.1 allows remote attackers to execute arbitrary code via a specially crafted HTTP POST request.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Uniguest Tripleplay versions prior to 24.2.1 contain an unauthenticated remote code execution vulnerability that can be exploited through specially crafted HTTP POST requests, allowing remote attackers to execute arbitrary code without any authentication credentials.

MitigationUpgrade Uniguest Tripleplay to version 24.2.1 or later to remediate this vulnerability. If immediate upgrading is not feasible, consider network segmentation and restricting external access to the affected service as a temporary mitigation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TripleplayApplication
Affected:< 24.1.2= 24.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Uniguest Tripleplay installation
    Locate the Uniguest Tripleplay application on the system by checking installed software, running services, or the web management interface URL path
    Affected if Uniguest Tripleplay is found to be installed on the system
  2. Determine installed version
    Access the system's version information through the management interface, command-line tools, or configuration files to retrieve the exact version number of Uniguest Tripleplay
    Affected if The retrieved version is less than 24.1.2, or exactly equals 24.2
  3. Verify web interface accessibility
    Check if the Uniguest Tripleplay HTTP management interface is reachable by accessing it via browser or curl command from a network location
    Affected if The management interface is accessible and responds to HTTP requests without requiring authentication
  4. Confirm vulnerability trigger method
    Send a crafted HTTP POST request to the management interface endpoint without providing any authentication credentials
    Affected if The system processes the unauthenticated POST request and accepts commands, indicating the vulnerability is present

A system is affected if Uniguest Tripleplay is running with a version less than 24.1.2 or exactly version 24.2, and the HTTP management interface accepts unauthenticated POST requests

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 24.1.2 or later
Fixed in 24.1.2
Interim mitigation

Upgrade Uniguest Tripleplay to version 24.2.1 or later to remediate this vulnerability. If immediate upgrading is not feasible, consider network segmentation and restricting external access to the affected service as a temporary mitigation.

Recommended fix High confidence

24.2.1 or later

  1. 1. Identify the current installed version of Uniguest Tripleplay
  2. 2. If the current version is less than 24.2.1 (including versions < 24.1.2 or version 24.2), plan for upgrade to version 24.2.1 or later
  3. 3. Review release notes for version 24.2.1 to confirm included security fixes
  4. 4. Schedule maintenance window for the upgrade
  5. 5. Perform backup of configuration and data according to Tripleplay backup procedures
  6. 6. Upgrade to Tripleplay version 24.2.1 or the latest stable release
  7. 7. Verify the upgrade was successful and the service is operational
  8. 8. Confirm the vulnerability is remediated by checking the new version number

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tripleplay Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50704 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-50704 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data