CVE-2001-0315
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe locking feature in mIRC 5.7 allows local users to bypass the password mechanism by modifying the LockOptions registry key.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn mIRC 5.7, the application's locking feature (intended to password-protect the client) can be bypassed by local users who modify the LockOptions registry key, allowing unauthorized access to the IRC client without knowing the configured password.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed mIRC versionCheck the Windows registry at HKLM\SOFTWARE\mIRC or look for mIRC in Programs and Features. Query: reg query "HKLM\SOFTWARE\mIRC" /v Version or check program files directory for mirc.exe and right-click for Properties > DetailsAffected if Installed version is 5.7 or any version lower than 5.7 (the vulnerability affects versions <= 5.7)
-
Locate the LockOptions registry keyOpen Registry Editor and navigate to HKCU\Software\mIRC\Lock or check HKLM\SOFTWARE\mIRC\Lock for the LockOptions valueAffected if The LockOptions registry key exists and contains configuration data (indicating the lock feature has been set up)
-
Check registry key permissions for standard usersRight-click the LockOptions registry key in regedit, select Permissions, and verify whether Users or standard non-admin accounts have Write or Full Control permissionsAffected if Standard (non-admin) users have Write or Modify permissions to the LockOptions registry key, allowing them to bypass the lock
User is affected if mIRC version 5.7 or lower is installed AND the locking feature is configured via LockOptions registry key AND standard users have write access to that registry key, allowing them to modify the lock configuration and bypass the password protection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade from mIRC 5.7 to a current supported version, or restrict write access to the mIRC registry keys via Windows Group Policy to prevent unprivileged users from modifying LockOptions.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-0315 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2001-0315 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data