CVE-2025-44649: In the configuration file of racoon in the TRENDnet TEW-WLC100P 2.03b03, the first item of exchage_mode is...
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.
Security readout for executives and security teams
Plain-English summary
This CVE describes an insecure default IPsec/IKE setting in the TRENDnet TEW-WLC100P 2.03b03 racoon configuration. Aggressive mode can expose identity information and make password guessing attacks easier. The business concern is confidentiality loss for environments using this controller’s VPN/IPsec configuration.
Executive priority
Prioritize review for any internet-facing or partner-facing controller using IPsec. Treat as high urgency where VPN identity confidentiality or shared-secret strength matters. If the product is not deployed, no direct action is indicated.
Technical view
The reported issue is that the first racoon exchange_mode value is set to aggressive. In IKE Phase 1, aggressive mode exposes identity data in plaintext, supports offline dictionary attack conditions, and weakens negotiation flexibility. CVSS is 7.5 with network access and no authentication required.
Likely exposure
Exposure appears limited to deployments of TRENDnet TEW-WLC100P version 2.03b03 using the affected racoon/IPsec configuration. The CVE affected-product metadata is incomplete and lists vendor, product, and CPE as n/a, so asset validation is necessary.
Exploitation context
The source bundle does not report active exploitation, and KEV is false. The risk is credible because aggressive mode is a known weak IKE Phase 1 configuration, but the provided sources do not prove public exploitation against this device.
Researcher notes
The record is sparse: affected CPE fields are n/a, and only the description names TRENDnet TEW-WLC100P 2.03b03. Analysis should stay tied to racoon IKE aggressive mode behavior and avoid assuming broader TRENDnet exposure or confirmed remediation.
Mitigation direction
Check TRENDnet guidance for patched firmware or configuration recommendations.
Disable IKE aggressive mode where supported by the product.
Prefer main mode or stronger vendor-supported IPsec settings.
Restrict IPsec/IKE exposure to trusted networks where operationally possible.
Rotate weak pre-shared keys if aggressive mode was enabled.
Validation and detection
Inventory TRENDnet TEW-WLC100P devices and confirm firmware version 2.03b03.
Review racoon configuration for exchange_mode using aggressive as the first value.
Confirm whether IPsec/IKE services are reachable from untrusted networks.
Check VPN logs for unusual or repeated IKE negotiation attempts.
Track vendor advisories because affected metadata and fixes are incomplete.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-312: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-312 · source CWE mapping
Cleartext Storage of Sensitive Information
Cleartext Storage of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.