What is the severity of CVE-2016-6870?

CVE-2016-6870 is considered a high severity vulnerability due to the risk of an out-of-bounds write affecting multiple functions.

How do I fix CVE-2016-6870?

To fix CVE-2016-6870, upgrade Facebook HHVM to version 3.15.0 or later.

What versions of HHVM are affected by CVE-2016-6870?

CVE-2016-6870 affects all versions of Facebook HHVM prior to 3.15.0, specifically up to version 3.14.5.

What functions are vulnerable in CVE-2016-6870?

CVE-2016-6870 impacts the mb_detect_encoding, mb_send_mail, and mb_detect_order functions.

Can CVE-2016-6870 be exploited remotely?

Yes, CVE-2016-6870 can be exploited remotely through unknown vectors, posing a security threat to applications using HHVM.

Vulnerability/
CVE-2016-6870

critical

9.8

CWE

787

17/2/2017

6/8/2024

CVE-2016-6870

First published: Fri Feb 17 2017(Updated: )

Out-of-bounds write in the (1) mb_detect_encoding, (2) mb_send_mail, and (3) mb_detect_order functions in Facebook HHVM before 3.15.0 allows attackers to have unspecified impact via unknown vectors.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Facebook HHVM	<=3.14.5

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-6870?
CVE-2016-6870 is considered a high severity vulnerability due to the risk of an out-of-bounds write affecting multiple functions.
How do I fix CVE-2016-6870?
To fix CVE-2016-6870, upgrade Facebook HHVM to version 3.15.0 or later.
What versions of HHVM are affected by CVE-2016-6870?
CVE-2016-6870 affects all versions of Facebook HHVM prior to 3.15.0, specifically up to version 3.14.5.
What functions are vulnerable in CVE-2016-6870?
CVE-2016-6870 impacts the mb_detect_encoding, mb_send_mail, and mb_detect_order functions.
Can CVE-2016-6870 be exploited remotely?
Yes, CVE-2016-6870 can be exploited remotely through unknown vectors, posing a security threat to applications using HHVM.

collector/nvd-index
agent/softwarecombine
agent/type
collector/mitre-cve
source/MITRE
agent/references
agent/severity
agent/remedy
agent/last-modified-date
agent/weakness
agent/author
agent/first-publish-date
agent/tags
agent/description
agent/event
agent/source
vendor/facebook
canonical/facebook hhvm
version/facebook hhvm/3.14.5

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-2016-6870?
CVE-2016-6870 is considered a high severity vulnerability due to the risk of an out-of-bounds write affecting multiple functions.
How do I fix CVE-2016-6870?
To fix CVE-2016-6870, upgrade Facebook HHVM to version 3.15.0 or later.
What versions of HHVM are affected by CVE-2016-6870?
CVE-2016-6870 affects all versions of Facebook HHVM prior to 3.15.0, specifically up to version 3.14.5.
What functions are vulnerable in CVE-2016-6870?
CVE-2016-6870 impacts the mb_detect_encoding, mb_send_mail, and mb_detect_order functions.
Can CVE-2016-6870 be exploited remotely?
Yes, CVE-2016-6870 can be exploited remotely through unknown vectors, posing a security threat to applications using HHVM.

CVE-2016-6870

Remedy

Remedy

Remedy

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-6870?

How do I fix CVE-2016-6870?

What versions of HHVM are affected by CVE-2016-6870?

What functions are vulnerable in CVE-2016-6870?

Can CVE-2016-6870 be exploited remotely?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2016-6870?

How do I fix CVE-2016-6870?

What versions of HHVM are affected by CVE-2016-6870?

What functions are vulnerable in CVE-2016-6870?

Can CVE-2016-6870 be exploited remotely?