CVE-2024-12642
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 · uneditedTenderDocTransfer from Chunghwa Telecom has an Arbitrary File Write 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 write arbitrary files to any path 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 · moderate confidenceTenderDocTransfer from Chunghwa Telecom exposes a local web server with APIs lacking CSRF protection, enabling unauthenticated remote attackers to conduct cross-site attacks via phishing. One API contains a Relative Path Traversal vulnerability allowing attackers to write arbitrary files to any location on the victim's filesystem.
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>= 0.41.151, < 0.41.157CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 if Cht Tenderdoctransfer is installedLocate the Tenderdoctransfer application on the system, typically found in installation directories or running as a service. Check running processes for 'Tenderdoctransfer' or 'TenderDocTransfer' processes.Affected if The application is present on the system
-
Determine the installed versionCheck the application version through its executable, configuration files, or service information. Compare the version number against the affected range: 0.41.151 to 0.41.156 (versions >= 0.41.151 and < 0.41.157).Affected if The installed version falls within 0.41.151 through 0.41.156 inclusive
-
Verify if local web server is running and accessibleCheck if the TenderDocTransfer application exposes a local web server (commonly on ports 8080, 8000, or similar). Attempt to access the web interface via localhost or local IP addresses.Affected if The local web server is running and accessible on network interfaces other than loopback only
-
Confirm API endpoints are reachable without authenticationProbe the application API endpoints (typically under /api/ paths) to verify they are accessible without requiring authentication or CSRF tokens.Affected if State-changing API endpoints are reachable without authentication
A user is affected if Cht Tenderdoctransfer version 0.41.151-0.41.156 is installed and its local web server is accessible, enabling unauthenticated path traversal attacks.
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.
dbcve · scoped0.41.157
Implement strict input validation with allowlist-based path sanitization to prevent path traversal, and add CSRF token protection to all state-changing APIs. Consider re-architecting to eliminate unnecessary local web server exposure or implementing authentication for the APIs.
0.41.157 or later
- Verify current installed version of TenderDocTransfer
- Download TenderDocTransfer version 0.41.157 or later from the official vendor (Chunghwa Telecom)
- Backup any existing TenderDocTransfer data and configuration files
- Uninstall the current vulnerable version (0.41.151-0.41.156)
- Install the fixed version 0.41.157 or later
- Verify the installation was successful and the application runs without errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12642 — 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-12642 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