dbcve.org
CWE-36Weakness · CWE-36

CVE-2024-12644

HIGH · 7.1 CVSS v3.1 Published 2024-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
The tbm-client from Chunghwa Telecom has an Arbitrary File vulnerability. The application sets up a simple local web server and provides APIs for communication with the target website. Due to the lack of CSRF protection in the APIs, unauthenticated remote attackers could use these APIs through phishing. Additionally, one of the APIs contains an Absolute Path Traversal vulnerability. Attackers can copy arbitrary files on the user's system and paste them into any path, which poses a potential risk of information leakage or could consume hard drive space by copying files in large volumes.

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 confidence

The tbm-client from Chunghwa Telecom sets up a local web server providing APIs for communication with target websites. The APIs lack CSRF protection, allowing unauthenticated remote attackers to exploit them through phishing attacks. Additionally, one API contains an Absolute Path Traversal vulnerability that enables attackers to copy arbitrary files from the user's system to any path, causing information leakage or disk space exhaustion.

MitigationImplement CSRF token validation on all APIs to prevent unauthorized requests, and fix the absolute path traversal vulnerability by validating and sanitizing file path inputs to restrict file operations to allowed directories.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
Low

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

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. Check if tbm-client from Chunghwa Telecom is installed
    Search for the tbm-client application in the system installed programs list or look for its installation directory. On Windows, check Program Files or AppData folders. On Linux/Mac, check common application directories.
    Affected if tbm-client is not installed on the system - the user is not affected.
  2. Verify if the local web server feature is enabled
    Locate the tbm-client configuration file (typically named config, settings, or similar in the application data directory) and check if the local web server option is turned on or if the service is running.
    Affected if the local web server is disabled or not running - the CSRF and path traversal vulnerabilities cannot be exploited.
  3. Identify the listening port for the local web server
    Check the tbm-client configuration for the port number (commonly defaults to a local port like 8080, 3000, or similar). Use 'netstat' or 'ss' command to verify the application is listening on that port.
    Affected if the local web server is listening on an open port - the vulnerable APIs are accessible for exploitation.
  4. Test for the CSRF vulnerability on exposed APIs
    Attempt to access the local web server APIs via browser or curl command (e.g., http://localhost:<port>/api/...) without providing any CSRF token. If the API responds successfully, the CSRF protection is missing.
    Affected if the APIs respond to requests without requiring any CSRF token - the user is affected by the CSRF vulnerability.
  5. Test for the Absolute Path Traversal vulnerability
    Locate the API endpoint that handles file operations (typically related to file copy, download, or backup functions). Send a request with an absolute path like '/etc/passwd' or 'C:\Windows\System32\config\sam' as the file parameter to see if the application accepts absolute paths outside its intended directory.
    Affected if the API accepts and processes absolute file paths - the user is affected by the path traversal vulnerability.

A user is affected if tbm-client is installed with the local web server enabled, making the CSRF-vulnerable APIs and the absolute path traversal API accessible to attackers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement CSRF token validation on all APIs to prevent unauthorized requests, and fix the absolute path traversal vulnerability by validating and sanitizing file path inputs to restrict file operations to allowed directories.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12644 — 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-12644 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