# CVE-2005-2025: Information disclosure in n/a

> Remote attackers can enumerate valid group names on Cisco VPN 3000 Concentrators by analyzing IKE Aggressive Mode responses.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m3gf-gx72-56g4

## What is CVE-2005-2025?

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

### Official description

Cisco VPN 3000 Concentrator before 4.1.7.F allows remote attackers to determine valid groupnames by sending an IKE Aggressive Mode packet with the groupname in the ID field, which generates a response if the groupname is valid, but does not generate a response for an invalid groupname.

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

It affects 8 products.


Products: Cisco Vpn 3000 Concentrator, Cisco Vpn 3000 Concentrator Series Software, Cisco Vpn 3005 Concentrator Software, Cisco Vpn 3015 Concentrator, Cisco Vpn 3020 Concentrator, Cisco Vpn 3030 Concentator, Cisco Vpn 3060 Concentrator, Cisco Vpn 3080 Concentrator.

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

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

## Is CVE-2005-2025 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-0427](https://insights.sbomify.com/CVE-2001-0427/): Denial of service in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2025 is a medium-severity vulnerability in n/a, published on 21 Jun 2005. 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-2005-2025 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-2005-2025/ (Markdown: https://insights.sbomify.com/CVE-2005-2025/index.md)
```

## Sources

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

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