CVE-2004-2612
First published: Fri Dec 31 2004(Updated: )
BNC 2.9.0 only grants access when an incorrect password is provided, which allows remote attackers to use the functionality intended for authorized users.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| BNC IRC | =2.9.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2004-2612?
CVE-2004-2612 is classified as a medium severity vulnerability due to its potential for unauthorized access.
How do I fix CVE-2004-2612?
To fix CVE-2004-2612, upgrade BNC from version 2.9.0 to a later version where this vulnerability is patched.
What systems are affected by CVE-2004-2612?
CVE-2004-2612 specifically affects BNC version 2.9.0.
Can CVE-2004-2612 be exploited remotely?
Yes, CVE-2004-2612 can be exploited by remote attackers to gain unauthorized access.
What functionalities are affected by CVE-2004-2612?
CVE-2004-2612 allows unauthorized users to access functionalities intended for authorized users.
- agent/type
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/references
- agent/weakness
- agent/severity
- agent/remedy
- agent/last-modified-date
- agent/description
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-historical
- agent/software-canonical-lookup-request
- collector/nvd-index
- vendor/bnc
- canonical/bnc irc
- version/bnc irc/2.9.0