dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-43662

MEDIUM · 5.3 CVSS v4.0 Published 2025-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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
The <redacted>.exe or <redacted>.exe CGI binary can be used to upload arbitrary files to /tmp/upload/ or /tmp/ respectively as any user, although the user interface for uploading files is only shown to the iocadmin user. This issue affects Iocharger firmware for AC models before version 24120701. Likelihood: Moderate – An attacker will need to have knowledge of this CGI binary, e.g. by finding it in firmware. Furthermore, the attacker will need a (low privilege) account to gain access to the <redacted>.exe or <redacted>.exe CGI binary and upload the file, or convince a user with such access to upload it. Impact: Low – The attacker can upload arbitrary files to /tmp/upload/ or /tmp/. However, the attacker is unable to access or use these files without other vulnerabilities. CVSS clarification. The attack can be executed over any network connection the station is listening to and serves the web interface (AV:N), and there are no additional security measure sin place that need to be circumvented (AC:L), the attack does not rely on preconditions (AT:N). The attack does require authentication, but the level of authentication is irrelevant (PR:L), it does not require user interaction (UI:N). Artitrary files can be uploaded, be these files will not be in a location where they can influence confidentiality or availability and have a minimal impact on device integrity (VC:N/VI:L/VA:N). There is no impact on subsequent systems. (SC:N/SI:N/SA:N). While this device is an EV charger handing significant amounts of power, we do not expect this vulnerability to have a safety impact. The attack can be automated (AU:Y).

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

The Iocharger AC firmware contains an unauthenticated file upload vulnerability in a CGI binary. Any authenticated user (including low-privilege users) can upload arbitrary files to /tmp/upload/ or /tmp/ directories via this CGI binary, regardless of whether the web UI shows the upload functionality to them.

MitigationUpdate Iocharger AC firmware to version 24120701 or later to remediate this vulnerability.

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
Low
Authentication
Y
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:X/RE:X/U:X

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 Iocharger AC firmware version
    Access the device admin interface and navigate to System > Firmware/About, or check the banner/login page for version information. Alternatively, check /etc/version or /etc/os-release via SSH if available.
    Affected if The installed version is earlier than 24120701, or if the version cannot be confirmed as 24120701 or later.
  2. Locate the vulnerable CGI upload binary
    Check for the existence of CGI binaries in the web server's cgi-bin or /cgi-bin/ directory. Common paths include /www/cgi-bin/upload, /cgi-bin/fileupload, or similar. Use 'find /www -name "*upload*"' or 'ls -la /www/cgi-bin/' via SSH.
    Affected if An upload-related CGI binary exists in the web directory structure.
  3. Verify upload directories exist and are writable
    Check for /tmp/upload/ and /tmp/ directories with 'ls -la /tmp/' or 'ls -la /tmp/upload/'. Confirm these directories are writable by the web server user (www-data, root, or charger user).
    Affected if The /tmp/upload/ or /tmp/ directories exist and are writable by the web server process.
  4. Check web server configuration for CGI handling
    Examine the web server configuration (lighttpd.conf, nginx.conf, or httpd.conf) for CGI script mappings. Look for 'cgi.assign' or 'script_alias' directives that map .cgi files to the upload endpoint.
    Affected if The web server is configured to execute CGI scripts and maps to an upload functionality.
  5. Confirm authenticated access enables the vulnerability
    Attempt to authenticate with any user account (even low-privilege) and verify the session is accepted by the CGI endpoint. Check if authentication bypass is not required (the summary states any authenticated user can exploit).
    Affected if Any valid user credentials provide access to the upload CGI endpoint.

A user is affected if they run Iocharger AC firmware version earlier than 24120701 and the upload CGI binary is accessible with authenticated user access.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Iocharger AC firmware to version 24120701 or later to remediate this vulnerability.

Recommended fix High confidence

24120701 or later

  1. Upgrade Iocharger AC firmware to version 24120701 or later to resolve the unrestricted file upload vulnerability

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,460
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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