CVE-2009-1803
UnknownEPSS 1.22%
Last modified
CVE-2009-1803 is a vulnerability of currently unknown severity. FreePBX 2.5.1, and other 2.4.x, 2.5.x, and pre-release 2.6.x versions, generates different error messages for a failed login attempt depending on whether the user account exists, which allows remote attackers to enumerate valid usernames.. EPSS estimates a 1.22% chance of exploitation in the next 30 days.
Description
FreePBX 2.5.1, and other 2.4.x, 2.5.x, and pre-release 2.6.x versions, generates different error messages for a failed login attempt depending on whether the user account exists, which allows remote attackers to enumerate valid usernames.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Freepbx | Freepbx | 2.4 |
| Freepbx | Freepbx | 2.4.0_beta1 |
| Freepbx | Freepbx | 2.4.0_beta2 |
| Freepbx | Freepbx | 2.4.1 |
| Freepbx | Freepbx | 2.5 |
| Freepbx | Freepbx | 2.5.0_beta1 |
| Freepbx | Freepbx | 2.5.0rc2 |
| Freepbx | Freepbx | 2.5.0rc3 |
| Freepbx | Freepbx | 2.5.1 |
| Freepbx | Freepbx | 2.5.2 |
| Sangoma | Freepbx | 2.4.0 |
| Sangoma | Freepbx | 2.5.0 |
References
- http://secunia.com/advisories/34772Vendor Advisory
- http://secunia.com/advisories/34772Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2009-1803?
FreePBX 2.5.1, and other 2.4.x, 2.5.x, and pre-release 2.6.x versions, generates different error messages for a failed login attempt depending on whether the user account exists, which allows remote attackers to enumerate valid usernames.
How severe is CVE-2009-1803?
Severity scoring for CVE-2009-1803 is pending analysis. The EPSS model estimates a 1.22% probability of exploitation in the next 30 days.
How do I fix CVE-2009-1803?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2009-1803?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
