LiveActive security incident?Get immediate response
CVE Record

CVE-2025-44647: In TRENDnet TEW-WLC100P 2.03b03, the i_dont_care_about_security_and_use_aggressive_mode_psk option is enabl...

In TRENDnet TEW-WLC100P 2.03b03, the i_dont_care_about_security_and_use_aggressive_mode_psk option is enabled in the strongSwan configuration file, so that IKE Responders are allowed to use IKEv1 Aggressive Mode with Pre-Shared Keys to conduct offline attacks on the openly transmitted hash of the PSK.

HighCVSS 7.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-44647 affects the reported TRENDnet TEW-WLC100P 2.03b03 configuration. It permits IKEv1 Aggressive Mode with pre-shared keys, which can expose a hash that attackers may try to crack offline. This mainly creates risk to VPN or IPsec secrets and related network access if weak keys are used.

Executive priority

Treat this as a high-priority network-edge configuration issue, especially if affected controllers expose VPN services externally. Business urgency depends on deployment count, internet exposure, and PSK strength. There is no sourced evidence of exploitation in the provided bundle.

Technical view

The source describes strongSwan configured with i_dont_care_about_security_and_use_aggressive_mode_psk enabled. That allows IKE responders to use IKEv1 Aggressive Mode with PSKs, exposing a PSK-derived hash for offline attack. CVSS v3.1 is 7.3, network exploitable, low complexity, no privileges or user interaction required.

Likely exposure

Exposure is most likely where TRENDnet TEW-WLC100P 2.03b03 is deployed with IPsec/IKE services reachable by untrusted networks. The provided affected-products metadata is incomplete, so scope should be verified against asset inventory and vendor records.

Exploitation context

The bundle does not cite active exploitation, and KEV is false. The described risk is offline guessing against an openly transmitted PSK hash, which becomes more serious when PSKs are weak, reused, or protect sensitive network paths.

Researcher notes

The CVE record gives a clear technical condition but incomplete affected-product metadata and no named patch. Validate against firmware 2.03b03 and the referenced configuration behavior. Avoid expanding scope beyond TRENDnet TEW-WLC100P unless vendor or CVE updates confirm it.

Mitigation direction

  • Check TRENDnet guidance for firmware or configuration updates.
  • Identify TEW-WLC100P 2.03b03 devices and prioritize exposed IKE/IPsec services.
  • Restrict IKE/IPsec reachability to trusted networks where operationally possible.
  • Rotate weak or reused PSKs after exposure assessment.
  • Prefer vendor-supported configurations that avoid IKEv1 Aggressive Mode with PSKs.

Validation and detection

  • Inventory TRENDnet TEW-WLC100P firmware versions in managed environments.
  • Review strongSwan or device VPN configuration for the named option.
  • Confirm whether IKE/IPsec services are internet reachable.
  • Check vendor advisories before declaring remediation complete.
  • Document PSK rotation status for affected VPN profiles.
Prepared
Confidence
medium
Sources
4

Public sources used

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.

cve · low confidence lookup

CVE-2025-44647 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2025-44647Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.