/

CVE-2024-55019

Severity:

HIGH RISK

(7.5)

Incorrect Access Control in Weintek cMT-3072XH2 easyweb

CVE-2024-55019

Analyzed

Vulnerability type

Category:

Incorrect Access Control

CWE:

CWE-284

Impact:

Unauthorized File Disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

An incorrect access control flaw in the download_wb.cgi component of the Weintek cMT-3072XH2 easyweb interface allows arbitrary file downloads without authentication.

An attacker who can reach the device's web interface may be able to retrieve sensitive files from the system, potentially exposing configuration data, credentials, or other confidential information.

Affected context

This vulnerability affects deployments of Weintek cMT-3072XH2 running easyweb Web Version v2.1.53 with OS v20231011 where the web management interface is accessible over the network.

The issue manifests in the download_wb.cgi download handler, which responds to requests for files without enforcing proper authentication or authorization checks.

Systems directly exposed to untrusted networks, or reachable from compromised internal hosts, are more susceptible to exploitation.

Exploit preconditions

  • Attack surface: HTTP(S) interface of the Weintek cMT-3072XH2 easyweb web server.
  • Required access: Network-level access to the device (no prior authentication required according to the description).
  • Trigger point: A crafted request to the download_wb.cgi endpoint specifying a target file.
  • Why exploitation is possible: The endpoint does not adequately verify the requester's identity or permissions before serving requested files, leading to missing or ineffective access control on file downloads.

Why this happens

The core issue is incorrect or missing access control (CWE-284) on the file download functionality implemented by download_wb.cgi.

The handler appears to trust incoming requests and serves files purely based on request parameters, without consistently enforcing authentication or authorization rules.

This pattern reflects a broader class of bugs where security-sensitive resources (such as configuration or system files) are exposed via web endpoints that either skip access checks or apply them only in limited cases, leaving a direct path for unauthenticated users to obtain protected data.

Potential impact

  • An attacker may download device configuration files, including network settings and operational parameters.
  • An attacker could obtain sensitive credentials or keys stored in readable configuration or log files.
  • Exposure of proprietary project files or application data used by the HMI.
  • Facilitation of follow-on attacks such as lateral movement in the OT/IT network based on recovered credentials or internal details.
  • Potential disclosure of information useful for targeting other vulnerabilities or tailoring attacks against the specific environment.

General mitigation guidance

Mitigation typically focuses on tightening access control around web-facing functionality and minimizing unnecessary exposure of the device.

Pattern-based defensive measures include:

  • Ensuring that all file download endpoints enforce robust authentication and authorization checks before serving any content.
  • Limiting which directories and file types are ever exposed through download handlers, using explicit allowlists rather than broad filesystem access.
  • Segmenting industrial devices onto dedicated network zones with strict firewall rules, restricting web interface access to trusted management hosts only.
  • Applying least-privilege principles to the web service process so that it can access only the minimal set of files required for normal operation.
  • Enabling secure configuration management practices so sensitive secrets are not stored in world-readable files on the device.

These measures reduce potential damage even if a specific download endpoint has logic flaws.

How teams detect issues like this

Detection approaches generally center on both code-level inspection and runtime monitoring:

  • Static review: Examine CGI scripts and web handlers for any file download logic that does not consistently verify authentication and authorization before accessing filesystem paths.
  • Pattern-based checks: Flag handlers that map request parameters directly to filesystem paths, especially where no user/session validation is visible.
  • Configuration and policy review: Confirm that access control policies for the web interface are documented and enforced, and that sensitive files are not unnecessarily readable by the web server process.
  • Runtime monitoring: Use network monitoring or web server logs to detect unusual patterns, such as repeated requests to download_wb.cgi or requests for unexpected internal paths.
  • Automated tools: Industrial/embedded-focused security scanners and generic web application security tools can be configured to probe for unauthenticated file download behaviors as part of regular assessments.

Sources

SourceLink
gist.github.comgist.github.com/AenganZ/f86ed0da28825a1432ec697f484622de
plain-trick-71d.notion.siteplain-trick-71d.notion.site/weintek-cMT-3072XH2-14687a89c4c181eeb21ad61e0392f34b?pvs=4

Frequently asked

questions

It can be, if the device's web interface is exposed to the internet or to an untrusted network segment. In many operational environments, exposure is intended to be limited, but any reachable interface from an attacker-controlled network can be a vector.

Based on the description, no. The flaw lies in missing or incorrect access control on download_wb.cgi, allowing unauthenticated requests to initiate file downloads.

Enforce strict authentication and authorization checks on all endpoints that access sensitive resources, particularly file download handlers, and restrict them to explicitly allowed files and user roles.

Adopt a secure design approach where every web endpoint is treated as potentially sensitive, require explicit access control in code reviews, avoid mapping user-supplied parameters directly to filesystem resources, and verify device exposure and network segmentation as part of deployment best practices.

Find out what's already
exploitable in your codebase.