What is the severity of CVE-2013-3796?

CVE-2013-3796 is considered a potential availability vulnerability in Oracle MySQL.

How do I fix CVE-2013-3796?

To fix CVE-2013-3796, you should upgrade to MySQL version 5.6.12 or later.

Who is affected by CVE-2013-3796?

CVE-2013-3796 affects remote authenticated users of Oracle MySQL versions 5.6.11 and earlier.

What types of systems are impacted by CVE-2013-3796?

CVE-2013-3796 impacts systems running Oracle MySQL Server version 5.6.11 or earlier.

Is there a workaround for CVE-2013-3796?

There are no publicly documented workarounds for CVE-2013-3796, and upgrading is recommended.

Vulnerability/
CVE-2013-3796

medium

17/7/2013

6/8/2024

CVE-2013-3796

First published: Wed Jul 17 2013(Updated: )

Unspecified vulnerability in the MySQL Server component in Oracle MySQL 5.6.11 and earlier allows remote authenticated users to affect availability via unknown vectors related to Server Optimizer.

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
MySQL	<=5.6.11
MySQL	=5.6.0
MySQL	=5.6.1
MySQL	=5.6.2
MySQL	=5.6.3
MySQL	=5.6.4
MySQL	=5.6.5
MySQL	=5.6.6
MySQL	=5.6.7
MySQL	=5.6.8
MySQL	=5.6.9
MySQL	=5.6.10

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2013-3796?
CVE-2013-3796 is considered a potential availability vulnerability in Oracle MySQL.
How do I fix CVE-2013-3796?
To fix CVE-2013-3796, you should upgrade to MySQL version 5.6.12 or later.
Who is affected by CVE-2013-3796?
CVE-2013-3796 affects remote authenticated users of Oracle MySQL versions 5.6.11 and earlier.
What types of systems are impacted by CVE-2013-3796?
CVE-2013-3796 impacts systems running Oracle MySQL Server version 5.6.11 or earlier.
Is there a workaround for CVE-2013-3796?
There are no publicly documented workarounds for CVE-2013-3796, and upgrading is recommended.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/severity
agent/references
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/oracle
canonical/mysql
version/mysql/5.6.11
version/mysql/5.6.0
version/mysql/5.6.1
version/mysql/5.6.2
version/mysql/5.6.3
version/mysql/5.6.4
version/mysql/5.6.5
version/mysql/5.6.6
version/mysql/5.6.7
version/mysql/5.6.8
version/mysql/5.6.9
version/mysql/5.6.10

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2013-3796?
CVE-2013-3796 is considered a potential availability vulnerability in Oracle MySQL.
How do I fix CVE-2013-3796?
To fix CVE-2013-3796, you should upgrade to MySQL version 5.6.12 or later.
Who is affected by CVE-2013-3796?
CVE-2013-3796 affects remote authenticated users of Oracle MySQL versions 5.6.11 and earlier.
What types of systems are impacted by CVE-2013-3796?
CVE-2013-3796 impacts systems running Oracle MySQL Server version 5.6.11 or earlier.
Is there a workaround for CVE-2013-3796?
There are no publicly documented workarounds for CVE-2013-3796, and upgrading is recommended.