CVE-2009-3727
Reported by redhat · Published November 10, 2009
Asterisk Open Source 1.2.x before 1.2.35, 1.4.x before 1.4.26.3, 1.6.0.x before 1.6.0.17, and 1.6.1.x before 1.6.1.9; Business Edition A.x.x, B.x.x before B.2.5.12, C.2.x.x before C.2.4.5, and C.3.x.x before C.3.2.2; AsteriskNOW 1.5; and s800i 1.3.x before 1.3.0.5 generate different error messages depending on whether a SIP username is valid, which allows remote attackers to enumerate valid usernames via multiple crafted REGISTER messages with inconsistent usernames in the URI in the To header and the Digest in the Authorization header.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
| n/a | n/a | * |
Timeline
- Nov 10, 2009 CVE Published
- Feb 4, 2022 EPSS Score (30 in total, the first dated here)
- Apr 8, 2026 Distribution Patch
- Apr 8, 2026 Security Advisory (2 in total, the first dated here)
- Jun 16, 2026 CVE Updated
- Nov 3, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2009-3727
vulnetix vdb fixes CVE-2009-3727Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2009-3727/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- 37265 third-party-advisoryx_refsource_SECUNIA
- FEDORA-2009-11126 vendor-advisoryx_refsource_FEDORA
- 37479 third-party-advisoryx_refsource_SECUNIA
- 37677 third-party-advisoryx_refsource_SECUNIA
- DSA-1952 vendor-advisoryx_refsource_DEBIAN
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- 36924 vdb-entryx_refsource_BID
- FEDORA-2009-11070 vendor-advisoryx_refsource_FEDORA
- 59697 vdb-entryx_refsource_OSVDB
- x_refsource_CONFIRM
- 1023133 vdb-entryx_refsource_SECTRACK