MySQLDatabase / datastore
CVE-2011-2262
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 · uneditedUnspecified vulnerability in the MySQL Server component in Oracle MySQL 5.1.x and 5.5.x allows remote attackers to affect availability via unknown vectors.
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 · low confidenceA remote denial-of-service vulnerability in Oracle MySQL Server versions 5.1.x and 5.5.x allows remote attackers to impact availability through unknown vectors. The specific attack mechanism and affected components are not detailed in the available documentation.
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
MySQLDatabase / datastore
= 5.1.5= 5.1.23= 5.1.31= 5.1.32= 5.1.34= 5.1.37
MySQLDatabase / datastore
= 5.1= 5.1.1= 5.1.2= 5.1.3= 5.1.4= 5.1.6= 5.1.7= 5.1.8= 5.1.9= 5.1.10= 5.1.11= 5.1.12CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 MySQL Server versionRun the command: mysql -V or mysqladmin version or SELECT VERSION(); from a MySQL client connectionAffected if The installed version matches MySQL 5.1.x or 5.5.x (including 5.1.5, 5.1.23, 5.1.31, 5.1.32, 5.1.34, 5.1.37, or any 5.1.x through 5.1.12, or any 5.5.x version before the patched releases)
-
Confirm MySQL service is network-accessibleCheck if the MySQL port (default 3306) is listening on non-localhost interfaces using: netstat -tuln | grep 3306 or ss -tuln | grep 3306Affected if MySQL is bound to 0.0.0.0 or a routable IP address rather than 127.0.0.1 only
-
Verify MySQL is runningCheck process status with: ps aux | grep mysql or systemctl status mysql (depending on OS)Affected if MySQL server process is active and accepting connections (the vulnerability can be triggered remotely)
-
Check MySQL configuration for bind-addressInspect my.cnf or my.ini for the bind-address directive under [mysqld] sectionAffected if bind-address is set to 0.0.0.0 or an external IP rather than 127.0.0.1
A user is affected if their MySQL Server is version 5.1.x or 5.5.x and the service is network-accessible to remote attackers.
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 MySQL Server to a patched version (5.1.60+ or 5.5.20+) to remediate this vulnerability. If immediate patching is not feasible, consider network segmentation to limit remote access to the MySQL service.
Fix this in MySQL
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2262 — 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-2011-2262 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