TRENDnet TEW-WLC100P
CVE-2025-44649
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach device IKE endpoint or on-path position
-
DeliveryInitiate or capture IKE Phase 1 aggressive exchange
-
ExploitExtract plaintext identity and PSK hash
-
ExecutionRun offline dictionary attack on hash
-
PersistRecover pre-shared key
-
ImpactImpersonate peer or decrypt IPsec traffic
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V14 - Data Protection Encrypted storage of sensitive data
|
| Exploitation Conditions | The device must be running firmware 2.03b03 with racoon configured such that exchange_mode lists aggressive as the first (selected) option - this is the shipped default configuration, so no non-default change is needed on the target. To gain value, the attacker must be able to either passively observe an IKE Phase 1 negotiation (requiring a man-in-the-middle or on-path network position) or actively initiate a Phase 1 handshake against the device's IKE endpoint (UDP 500/4500 reachable). Successful PSK recovery is further limited by PSK strength: a long, random pre-shared key makes the offline dictionary attack computationally infeasible, so the practical impact hinges on a weak/guessable PSK. Identity disclosure itself occurs whenever aggressive mode is negotiated, with no authentication required. |
| Impact | The NVD CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, 7.5) rates this High and network-exploitable with confidentiality-only impact, which aligns with the information-disclosure nature of aggressive mode. However, that AV:N/AC:L/PR:N framing likely overstates ease: realistic exploitation requires the attacker to either passively intercept an IKE negotiation (privileged network position) or actively initiate a Phase 1 handshake with the device, and the damaging outcome - PSK recovery - is contingent on the PSK being weak enough to crack offline. Corroborating low-urgency signals: EPSS is 0.27% (19th percentile), the CVE is not in CISA KEV, and no SSVC decision data or verified POC is provided. The two references are researcher writeups (a GitHub gist and a Notion page), not a vendor advisory, so patch and formal exploit status are unconfirmed. Net: a legitimate hardening defect worth fixing on affected appliances, but not an emergency - treat as medium-priority absent evidence of a weak PSK or active targeting. Note the tension to verify: CVSS implies trivial network compromise, while the underlying weakness practically depends on an observed/initiated negotiation and a guessable PSK. |
| Exploit ScenarioDerived | An attacker positioned to intercept traffic to the TEW-WLC100P, or able to reach its IKE service, initiates or captures an IKE Phase 1 aggressive-mode exchange and records the plaintext identity payload plus the responder's PSK-derived hash. They then run an offline dictionary/brute-force attack against the hash; if the pre-shared key is weak, they recover it and can impersonate a VPN peer or decrypt subsequent IPsec traffic. No POC is confirmed in the provided data, though the low attack complexity (AC:L) means capturing the exposed data is straightforward once a negotiation is observed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 05, 2026
Cleartext identity exposure in the TRENDnet TEW-WLC100P wireless controller (firmware 2.03b03) stems from its bundled racoon IKE daemon shipping with aggressive mode as the first exchange_mode entry. Because IKE Phase 1 aggressive mode transmits identity payloads in plaintext and sends a hash of the pre-shared key that can be captured, any party observing or initiating a negotiation can harvest identities and mount offline dictionary attacks against the PSK. No public exploit identified at time of analysis and the EPSS probability is low (0.27%, 19th percentile), consistent with a configuration-hardening weakness rather than a mass-exploited flaw.
RemediationAI
No vendor-released patch identified at time of analysis; check TRENDnet for a firmware update superseding 2.03b03 before deploying compensating controls. The primary compensating control is to reconfigure the racoon daemon to remove aggressive mode and use main mode exclusively - edit racoon.conf so exchange_mode is set to main (removing or reordering the aggressive entry), which protects identity payloads and eliminates the offline PSK hash exposure, at the cost of a slightly slower Phase 1 handshake and potential incompatibility with peers that only support aggressive mode. If aggressive mode cannot be disabled (for example, when a remote peer requires it), enforce a long, high-entropy pre-shared key or migrate to certificate-based authentication to defeat offline dictionary attacks, and restrict IKE/IPsec (UDP 500/4500) reachability to known peer IPs via firewall rules to limit who can initiate or observe negotiations. Consult the researcher writeups (the GitHub gist and Notion page above) for configuration specifics, but validate any change against vendor guidance since these are not official advisories.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is racoon, the IKEv1 key-management daemon (historically from the ipsec-tools/KAME project) used to establish IPsec Security Associations. IKE Phase 1 supports two exchange modes: main mode, which protects identity payloads inside an encrypted exchange, and aggressive mode, which compresses the handshake into three messages and sends the initiator/responder identity and a PSK-derived hash before an encrypted channel is established. Setting aggressive as the first exchange_mode in racoon.conf makes the device negotiate this weaker mode. This maps to CWE-312 (Cleartext Storage/Transmission of Sensitive Information): the identity and the material enabling a PSK guessing attack are exposed without confidentiality protection. The single affected build is identified by cpe:2.3:o:trendnet:tew-wlc100p_firmware:2.03b03.
Know when Tew Wlc100P Firmware gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Identity/PSK-hash exposure is remotely observable or triggerable with no auth (AV:N/AC:L/PR:N); confidentiality-only impact (C:H, I/A:N), matching the information-disclosure nature and no scope change.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
DescriptionCVE.org
In the configuration file of racoon in the TRENDnet TEW-WLC100P 2.03b03, the first item of exchage_mode is set to aggressive. Aggressive mode in IKE Phase 1 exposes identity information in plaintext, is vulnerable to offline dictionary attacks, and lacks flexibility in negotiating security parameters.
Executive ViewAI
TRENDnet TEW-WLC100P wireless controllers running firmware 2.03b03 transmit IKE pre-shared key identities in cleartext during negotiation, enabling network-adjacent attackers to harvest credentials and conduct offline dictionary attacks. Organizations using this controller for wireless network security face direct risk of unauthorized access and potential data exfiltration. While no public exploits currently exist, this configuration weakness requires immediate remediation to prevent compromise of wireless network perimeter security.
Disable IKE aggressive mode in racoon configuration file and enforce main mode only; implement network-level access controls restricting UDP 500 to trusted management networks; segment wireless controller management interfaces on dedicated VLANs; strengthen pre-shared keys to maximum length (32+ characters) and complexity; monitor IKE traffic logs for repeated negotiation failures indicating dictionary attack attempts; disable IKE on controller WAN interfaces if not required for remote management.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
NVD
CVE.org
EPSS
GitHub
Exploit-DB