CVE-2017-10788
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 DBD::mysql module through 4.043 for Perl allows remote attackers to cause a denial of service (use-after-free and application crash) or possibly have unspecified other impact by triggering (1) certain error responses from a MySQL server or (2) a loss of a network connection to a MySQL server. The use-after-free defect was introduced by relying on incorrect Oracle mysql_stmt_close documentation and code examples.
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 confidenceThe DBD::mysql Perl module through version 4.043 contains a use-after-free vulnerability triggered when the MySQL server returns certain error responses or when network connectivity is lost. The vulnerability stems from incorrect assumptions about mysql_stmt_close behavior based on flawed Oracle documentation, leading to memory corruption that can cause denial of service or potentially allow arbitrary code execution.
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<= 4.043CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 DBD::mysql is installedRun 'perl -MDBD::mysql -e 'print $DBD::mysql::VERSION'' or 'perldoc DBD::mysql' to see the versionAffected if DBD::mysql is installed and version is 4.043 or lower
-
Identify the Perl DBD::mysql package versionUse 'cpan -D DBD::mysql' or check your system's package manager for the installed DBD::mysql package versionAffected if The installed version number is 4.043 or any lower version number
-
Verify MySQL prepared statement usageReview Perl application code for usage of prepare(), execute(), or stmt_* methods against MySQL databases (e.g., $dbh->prepare(), $sth->execute())Affected if The application uses prepared statements against a MySQL server and DBD::mysql version is <= 4.043
-
Check for error handling code pathsSearch Perl code for eval blocks or error handling around DBD::mysql statement execution, or monitor for MySQL server error responsesAffected if The application handles MySQL errors or experiences connection issues while using DBD::mysql <= 4.043
A system is affected if DBD::mysql version 4.043 or lower is installed and the application uses MySQL prepared statements or encounters error responses from the 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.
dbcve · scopedUpgrade DBD::mysql to a version newer than 4.043 to obtain the patched code that correctly handles MySQL error responses and connection loss scenarios.
DBD::mysql 4.044 or later
- Check current DBD::mysql version: perl -MDBD::mysql -e 'print $DBD::mysql::VERSION'
- Upgrade DBD::mysql to version 4.044 or later using CPAN: cpan DBD::mysql
- Or upgrade using cpanm: cpanm DBD::mysql
- Verify the upgrade was successful by checking the version again
- Test your application to ensure it functions correctly with the updated module
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10788 — 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-2017-10788 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