CVE-2024-12645
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 · uneditedThe topm-client from Chunghwa Telecom has an Arbitrary File Read 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 for the APIs, unauthenticated remote attackers could use these APIs through phishing. Additionally, one of the APIs contains a Relative Path Traversal vulnerability, allowing attackers to read arbitrary files on the user's system.
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 confidenceThe topm-client from Chunghwa Telecom runs a local web server with APIs that lack CSRF protection. Combined with a relative path traversal vulnerability in one API, unauthenticated remote attackers can trick users into visiting malicious pages that trigger API calls to read arbitrary files from the victim's file system.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Verify topm-client installationCheck if the topm-client application is installed on the system by searching for the executable or service (e.g., search for 'topm-client' in program directories or running processes)Affected if topm-client is installed and running as a local web server service
-
Confirm local web server is activeIdentify which port the local web server listens on (typically localhost ports) by reviewing the application's configuration files or checking active network listenersAffected if The topm-client local web server is actively running and accessible
-
Identify vulnerable API endpointLocate API documentation, configuration, or traffic logs to identify endpoints that accept file path parameters (often endpoints related to file reading, downloading, or configuration loading)Affected if An API endpoint accepts file path parameters without validation
-
Test for path traversal vulnerabilitySend a crafted request to the suspected API with relative path sequences (e.g., ../../etc/passwd or ..\..\windows\system32\config\sam) to see if arbitrary file access is possibleAffected if The API returns content from files outside the intended directory, indicating path traversal is possible
-
Verify absence of CSRF protectionExamine the API requests and responses for anti-CSRF tokens, SameSite cookie attributes, or Origin/Referer header validation; also check if the application sets security headers like CSRF-TokenAffected if APIs lack anti-CSRF tokens and do not validate Origin or Referer headers, allowing cross-site request forgery
A user is affected if topm-client is installed with its local web server enabled, the vulnerable file-path API accepts relative path traversal sequences, and CSRF protections are missing, allowing remote attackers to read arbitrary files through tricked user browsers.
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 dataImplement CSRF protection (e.g., anti-CSRF tokens) on all APIs and apply strict input validation/sanitization to prevent path traversal attacks when handling file path parameters.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12645 — 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-12645 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