# CVE-2025-44647: Weak cryptography in n/a

> Enabling aggressive mode PSK in strongSwan allows offline attacks on the pre-shared key hash, exposing credentials.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-4gcv-68wg-8j74

## What is CVE-2025-44647?

CVE-2025-44647 is a high-severity vulnerability in n/a, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2025-44647?

It affects 1 product.


Products: Trendnet Tew-Wlc100p Firmware.

## How do I fix CVE-2025-44647?

No fix has been published for CVE-2025-44647 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-44647 being exploited?

There is no known exploitation of CVE-2025-44647 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-44649](https://insights.sbomify.com/CVE-2025-44649/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-44647 and fix it if it is affected.

What it is: CVE-2025-44647 is a high-severity vulnerability in n/a, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-44647 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-44647/ (Markdown: https://insights.sbomify.com/CVE-2025-44647/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-44647
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-44647
- OSV: https://osv.dev/vulnerability/CVE-2025-44647

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-44647/
Summaries are generated and may contain mistakes; the official description above is the record.