CyberSecBulletin
CVE-2025-41717NVD status: Deferred

TC ROUTER 3002T-3G: Improper Control of Generation of Code

Published Updated By the CyberSecBulletin desk

CVE-2025-41717 is a high-severity improper control of generation of code vulnerability in TC ROUTER 3002T-3G from Phoenix Contact, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 3.08.8 as the first without the flaw, so updating TC ROUTER 3002T-3G to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.55% 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 TC ROUTER 3002T-3G to 3.08.8 or a later version.
  2. Update TC ROUTER 2002T-3G to 3.08.8 or a later version.
  3. Update TC ROUTER 3002T-4G to 3.08.8 or a later version.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
  5. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
Phoenix ContactTC ROUTER 3002T-3Gbefore 3.08.83.08.8
Phoenix ContactTC ROUTER 2002T-3Gbefore 3.08.83.08.8
Phoenix ContactTC ROUTER 3002T-4Gbefore 3.08.83.08.8
Phoenix ContactTC ROUTER 3002T-4G GLbefore 3.08.83.08.8
Phoenix ContactTC ROUTER 5004T-5G EUbefore 1.06.231.06.23
Phoenix ContactTC ROUTER 3002T-4G VZWbefore 3.08.83.08.8
Phoenix ContactTC ROUTER 3002T-4G ATTbefore 3.08.83.08.8
Phoenix ContactTC ROUTER 2002T-4Gbefore 3.08.83.08.8
Phoenix ContactCLOUD CLIENT 1101T-TX/TXbefore 3.07.73.07.7
Phoenix ContactTC CLOUD CLIENT 1002-4G ATTbefore 3.08.83.08.8
Phoenix ContactTC CLOUD CLIENT 1002-TX/TXbefore 3.07.73.07.7

Version data comes from the organisation that assigned the CVE. 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
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
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:N/UI:R/S:U/C:H/I:H/A:H. Scored by CNA (cert.vde.com).

Official description

An unauthenticated remote attacker can trick a high privileged user into uploading a malicious payload via the config-upload endpoint, leading to code injection as root. This results in a total loss of confidentiality, availability and integrity due to improper control of code generation ('Code Injection’).

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: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Control of Generation of Code vulnerabilities

Spotted an error? Tell us.