CVE-2012-3441
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 database creation script (module/idoutils/db/scripts/create_mysqldb.sh) in Icinga 1.7.1 grants access to all databases to the icinga user, which allows icinga users to access other databases via unspecified 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 · moderate confidenceIn Icinga 1.7.1, the database creation script (create_mysqldb.sh) incorrectly grants the icinga MySQL user privileges to access ALL databases on the MySQL server, rather than restricting access to only the icinga database. This horizontal privilege escalation allows the icinga application user to read or modify data in other unrelated databases hosted on the same MySQL server.
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= 1.7.1CVSS 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 Icinga versionRun 'icinga --version' or check the package version installed on the system (e.g., dpkg -l icinga-core, rpm -q icinga-core)Affected if The installed version is exactly 1.7.1
-
Locate the MySQL creation scriptSearch for create_mysqldb.sh in the Icinga installation directory, commonly found in /usr/local/icinga/etc/ or /etc/icinga/Affected if The script grants 'ON *.*' or 'ON all_databases' to the icinga MySQL user instead of 'ON icinga.*'
-
Query current MySQL user privilegesConnect to MySQL as an administrator and run: SHOW GRANTS FOR 'icinga'@'localhost'; and SHOW GRANTS FOR 'icinga'@'%';Affected if The grants include privileges on databases other than the icinga database (e.g., 'ON *.*' or 'ON otherdb.*')
-
Verify access to non-icinga databasesAs the icinga MySQL user, attempt to list or access other databases: mysql -u icinga -p -e 'SHOW DATABASES;' and mysql -u icinga -p -e 'USE mysql; SELECT user, host, db FROM db;'Affected if The icinga user can see or access databases other than the icinga database
A system is affected if Icinga 1.7.1 is installed and the icinga MySQL user has privileges extending beyond the icinga database to other databases on the same MySQL server.
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 dataModify the create_mysqldb.sh script to grant privileges only to the specific icinga database (e.g., GRANT ALL PRIVILEGES ON icinga.* TO 'icinga'@'localhost'), then audit and revoke any excessive database privileges currently in production.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3441 — 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-2012-3441 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