CVE-2024-48747
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 · uneditedAn issue in alist-tvbox v1.7.1 allows a remote attacker to execute arbitrary code via the /atv-cli file.
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 · moderate confidencealist-tvbox v1.7.1 contains a remote code execution vulnerability via the /atv-cli endpoint. Attackers can inject and execute arbitrary system commands by leveraging insufficient input validation on this file-based endpoint, leading to complete server compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify alist-tvbox installationSearch for alist-tvbox processes, services, containers, or installed binaries. Check running processes with 'ps aux | grep alist-tvbox', list Docker containers with 'docker ps -a | grep alist', or look for the binary in common paths like /usr/local/bin, /opt, or the application working directory.Affected if alist-tvbox is found running or installed on the system
-
Verify alist-tvbox versionRun the version command if available, such as 'alist-tvbox --version' or 'alist-tvbox -v'. If running in Docker, inspect the image tag. Check the application's startup logs for version information.Affected if The installed version is 1.7.1 or earlier (no patched version range was specified)
-
Confirm /atv-cli endpoint is accessibleTest if the /atv-cli endpoint is reachable by sending a request: curl -X POST http://localhost:PORT/atv-cli -d 'test' (replace PORT with your application's port). Also verify network exposure by checking firewall rules, reverse proxy configurations, or cloud security groups.Affected if The /atv-cli endpoint responds to HTTP POST requests (even with error responses indicating the endpoint exists)
-
Check for authentication on the endpointReview application configuration files, API gateway settings, or middleware that controls access to /atv-cli. Determine if unauthenticated requests are permitted to this endpoint.Affected if No authentication, IP allowlisting, or access controls are required to reach /atv-cli
The environment is affected if alist-tvbox version 1.7.1 or earlier is installed AND the /atv-cli endpoint is network-accessible without proper authentication controls.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataRestrict network access to the /atv-cli endpoint immediately via firewall or access controls; if a patched version is available, upgrade. Otherwise, implement strict input sanitization and command validation on the endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48747 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-48747 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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