CVE-2017-10789
First published: Sat Jul 01 2017(Updated: )
The DBD::mysql module through 4.043 for Perl uses the mysql_ssl=1 setting to mean that SSL is optional (even though this setting's documentation has a "your communication with the server will be encrypted" statement), which allows man-in-the-middle attackers to spoof servers via a cleartext-downgrade attack, a related issue to CVE-2015-3152.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| dbd-mysql | <=4.043 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-10789?
CVE-2017-10789 has a severity rating that indicates a significant risk of man-in-the-middle attacks due to improper handling of SSL settings.
How do I fix CVE-2017-10789?
To fix CVE-2017-10789, upgrade the DBD::mysql module to version 4.044 or higher where this vulnerability is addressed.
What systems are affected by CVE-2017-10789?
CVE-2017-10789 affects versions of the DBD::mysql module through 4.043 for Perl.
What type of attack does CVE-2017-10789 allow?
CVE-2017-10789 allows man-in-the-middle attackers to potentially spoof servers by exploiting the SSL optionality.
Is SSL encryption mandatory with CVE-2017-10789?
No, due to the vulnerability in CVE-2017-10789, the mysql_ssl=1 setting incorrectly allows SSL to be optional.
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/last-modified-date
- agent/severity
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/dbd-mysql project
- canonical/dbd-mysql
- version/dbd-mysql/4.043