dbcve.org
Tc Mguard Rs4000 4g Vzw Vpn FirmwareOperating system · Phoenixcontact

CVE-2024-43385

HIGH · 8.8 CVSS v3.1 Published 2024-09-10
Fix available
A fix is available. Upgrade to 8.9.3 or later.
See remediation →
94/100
Remediation priority · Urgent
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
A low privileged remote attacker can trigger the execution of arbitrary OS commands as root due to improper neutralization of special elements in the variable PROXY_HTTP_PORT in mGuard devices.

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

This is a command injection vulnerability in mGuard devices where the PROXY_HTTP_PORT environment variable is not properly sanitized, allowing a low-privileged remote attacker to inject arbitrary OS commands that execute with root privileges.

MitigationApply vendor patches when available; in the interim, restrict network access to the mGuard management interface and disable unnecessary proxy services to reduce attack surface.

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
Tc Mguard Rs4000 4g Vzw Vpn FirmwareOperating system
Affected:< 8.9.3
Tc Mguard Rs4000 4g Vpn FirmwareOperating system
Affected:< 8.9.3
Tc Mguard Rs4000 4g Att Vpn FirmwareOperating system
Affected:< 8.9.3
Tc Mguard Rs4000 3g Vpn FirmwareOperating system
Affected:< 8.9.3
Tc Mguard Rs2000 4g Vzw Vpn FirmwareOperating system
Affected:< 8.9.3
Tc Mguard Rs2000 4g Vpn FirmwareOperating system
Affected:< 8.9.3
Tc Mguard Rs2000 4g Att Vpn FirmwareOperating system
Affected:< 8.9.3
Tc Mguard Rs2000 3g Vpn FirmwareOperating system
Affected:< 8.9.3

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the mGuard device model
    Access the mGuard management interface or check the device label to confirm the exact model number (e.g., RS4000 4G VPN, RS2000 4G VZW VPN)
    Affected if The device is one of the affected models: Tc Mguard RS4000 or RS2000 variants (4G, 3G, VZW, ATT)
  2. Check the installed firmware version
    Log into the mGuard management interface and navigate to the status or system information page to view the firmware version, or use the vendor's CLI command to retrieve the version
    Affected if The firmware version is lower than 8.9.3 (for example, 8.8.x, 8.7.x, etc.)
  3. Verify if the HTTP proxy service is enabled
    Access the mGuard management interface and check the proxy or services configuration settings to determine if the HTTP proxy functionality is enabled
    Affected if The HTTP proxy service is enabled and accessible to the attacker
  4. Inspect proxy-related environment variables
    If you have CLI or diagnostic access, examine the PROXY_HTTP_PORT environment variable configuration and any custom proxy settings for unexpected or injected characters
    Affected if The PROXY_HTTP_PORT variable contains shell metacharacters or unexpected values not set by the administrator

You are affected if you are running an mGuard RS2000 or RS4000 variant with firmware version below 8.9.3 and the HTTP proxy service is enabled, allowing an attacker to manipulate the PROXY_HTTP_PORT environment variable for command injection.

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
Upgrade available Upgrade to 8.9.3 or later
Fixed in 8.9.3
Interim mitigation

Apply vendor patches when available; in the interim, restrict network access to the mGuard management interface and disable unnecessary proxy services to reduce attack surface.

Recommended fix Moderate confidence

Tc Mguard firmware 8.9.3 or later (Rs2000 and Rs4000 series variants)

  1. 1. Obtain the firmware version 8.9.3 or later from the official Tc Mguard vendor (cert.vde.com or vendor support portal)
  2. 2. Log in to the mGuard device management interface with administrative credentials
  3. 3. Navigate to the firmware update section (typically under System Maintenance or Administration)
  4. 4. Upload the firmware image file (8.9.3 or later)
  5. 5. Confirm the firmware upgrade and allow the device to reboot
  6. 6. After reboot, verify the firmware version has been updated to 8.9.3 or later
  7. 7. Verify that the PROXY_HTTP_PORT configuration is functioning correctly
Caveat Review vendor release notes for any configuration or feature changes between current and 8.9.3 firmware versions before upgrading

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

Fix this in Tc Mguard Rs4000 4g Vzw Vpn Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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