CyberSecBulletin
CVE-2024-43392NVD status: Modified

FL MGUARD 2102: Improper Control of Generation of Code

Published Updated By the CyberSecBulletin desk

CVE-2024-43392 is a high-severity improper control of generation of code vulnerability in FL MGUARD 2102 from Phoenix Contact, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 10.4.1 as the first without the flaw, so updating FL MGUARD 2102 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.52% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update FL MGUARD 2102 to 10.4.1 or a later version.
  2. Update FL MGUARD 2105 to 10.4.1 or a later version.
  3. Update FL MGUARD 4102 PCI to 10.4.1 or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
PHOENIX CONTACTFL MGUARD 2102before 10.4.110.4.1
PHOENIX CONTACTFL MGUARD 2105before 10.4.110.4.1
PHOENIX CONTACTFL MGUARD 4102 PCIbefore 10.4.110.4.1
PHOENIX CONTACTFL MGUARD 4102 PCIEbefore 10.4.110.4.1
PHOENIX CONTACTFL MGUARD 4302before 10.4.110.4.1
PHOENIX CONTACTFL MGUARD 4305before 10.4.110.4.1
PHOENIX CONTACTFL MGUARD CENTERPORT VPN-1000before 8.9.38.9.3
PHOENIX CONTACTFL MGUARD CORE TXbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD CORE TX VPNbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD DELTA TX/TXbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD DELTA TX/TX VPNbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD GT/GTbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD GT/GT VPNbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD PCI4000before 8.9.38.9.3
PHOENIX CONTACTFL MGUARD PCI4000 VPNbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD PCIE4000before 8.9.38.9.3
PHOENIX CONTACTFL MGUARD PCIE4000 VPNbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD RS2000 TX/TX-Bbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD RS2000 TX/TX VPNbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD RS2005 TX VPNbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD RS4000 TX/TXbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD RS4000 TX/TX-Mbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD RS4000 TX/TX-Pbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD RS4000 TX/TX VPNbefore 8.9.38.9.3
PHOENIX CONTACTFL MGUARD RS4004 TX/DTXbefore 8.9.38.9.3

Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.1HighCNA (cert.vde.com)
CVSS 3.18.1HighNVD

Official description

A low privileged remote attacker can perform configuration changes of the firewall services, including packet filter, packet forwarding, network access control or NAT through the FW_INCOMING.FROM_IP FW_INCOMING.IN_IP FW_OUTGOING.FROM_IP FW_OUTGOING.IN_IP environment variable which can lead to a DoS.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Control of Generation of Code

The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

How developers prevent this class of flaw

  • Refactor your program so that you do not have to dynamically generate code.
  • Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
  • Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.

More Improper Control of Generation of Code vulnerabilities (CWE-94)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in FL MGUARD 2102

All FL MGUARD 2102 vulnerabilities

Recent Improper Control of Generation of Code vulnerabilities

Spotted an error? Tell us.