CVE-2013-3475
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 · uneditedStack-based buffer overflow in db2aud in the Audit Facility in IBM DB2 and DB2 Connect 9.1, 9.5, 9.7, 9.8, and 10.1, as used in Smart Analytics System 7600 and other products, allows local users to gain privileges 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 · high confidenceStack-based buffer overflow in the db2aud (DB2 Audit Facility) component allows local authenticated users to execute arbitrary code with elevated privileges by overflowing a stack buffer through unspecified vectors in DB2 versions 9.1 through 10.1.
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= 9.1= 9.5= 9.7= 9.8= 10.1= 9.1= 9.5= 9.7= 9.8= 10.1all versionsCVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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.
-
Check if DB2 is installedRun 'db2level' or 'db2pd -version' to query the DB2 version, or look for DB2 installation directories such as /opt/IBM/db2 or C:\Program Files\IBM\DB2Affected if DB2 software is found on the system
-
Verify DB2 version falls within affected rangeParse the version output from 'db2level' - look for versions 9.1, 9.5, 9.7, 9.8, or 10.1Affected if The installed version is 9.1, 9.5, 9.7, 9.8, or 10.1 (versions 9.1 through 10.1)
-
Confirm DB2 Audit Facility (db2aud) is presentCheck for the db2aud binary in the DB2 installation directory (typically in sqllib/bin or similar) or run 'db2audit describe' to query audit configurationAffected if The db2aud binary exists and the audit facility is configured or available on the system
-
Assess local authenticated accessDetermine if any local OS user has DB2 authentication credentials (e.g., check for DB2 users in the OS, review db2dascfg settings, or check db2diag.log for authentication events)Affected if A local user has valid DB2 authentication (DB2 username/password) to connect to the database
The environment is affected if DB2 version 9.1 through 10.1 is installed, the db2aud (Audit Facility) component is present, and a local authenticated user can interact with the DB2 system.
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 dataApply IBM DB2 security patches for this vulnerability; restrict local access to DB2 systems and follow least-privilege principles for DB2 user accounts.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3475 — 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-2013-3475 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