CVE-2017-1000381: memory overread when parsing invalid NAPTR responses

Published Jul 7, 2017
·
Updated

The c-ares function aresparsenaptrreply(), which is used for parsing NAPTR responses, could be triggered to read memory outside of the given input buffer if the passed in DNS response packet was crafted in a particular way.

Other sources

The c-ares function aresparsenaptrreply(), which is used for parsing NAPTR responses, could be triggered to read memory outside of the given input buffer if the passed in DNS response packet was crafted in a particular way.

— Node.Js

Affected Software

48 affected componentsFixes available
c-ares c-ares=1.8.0
c-ares c-ares=1.9.0
c-ares c-ares=1.9.1
c-ares c-ares=1.10.0
c-ares c-ares=1.12.0
C-ares Project C-ares=1.11.0
C-ares Project C-ares=1.11.0-rc1
Nodejs Node.js>=4.0.0<=4.1.2
Nodejs Node.js>=4.2.0<4.8.4
Nodejs Node.js>=5.0.0<=5.12.0
Nodejs Node.js>=6.0.0<=6.8.1
Nodejs Node.js>=6.9.0<6.11.1
Nodejs Node.js>=7.0.0<7.10.1
Nodejs Node.js>=8.0.0<8.1.4
F5 BIG-IP>=17.5.0<=17.5.1, >=17.1.0<=17.1.2
17.5.1.217.1.3
F5 BIG-IP>=16.1.0<=16.1.6
16.1.6.1
F5 BIG-IP>=15.1.0<=15.1.10
15.1.10.8
Node.js Node.js>=4.0.0<4.8.4, >=5.0.0<6.0.0, >=6.0.0<6.11.1, >=7.0.0<7.10.1, >=8.0.0<8.1.4
4.8.46.11.17.10.18.1.4
Node.js Node.js>=4.0.0<4.8.4
4.8.4
Node.js Node.js>=6.0.0<6.11.1
6.11.1
Node.js Node.js>=7.0.0<7.10.1
7.10.1
Node.js Node.js>=8.0.0<8.1.4
8.1.4
alpine/c-ares<1.12.0-r1
1.12.0-r1
alpine/c-ares<1.12.0-r1
1.12.0-r1
alpine/c-ares<1.12.0-r1
1.12.0-r1
alpine/c-ares<1.12.0-r1
1.12.0-r1
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.7.0-r1
6.7.0-r1
alpine/nodejs<6.9.5-r1
6.9.5-r1
alpine/nodejs<6.10.3-r1
6.10.3-r1
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs<6.11.1-r0
6.11.1-r0
alpine/nodejs-current<7.10.1-r0
7.10.1-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 17.5.1.217.1.3
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.1.6.1
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 15.1.10.8
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4Fixed in 6.11.1Fixed in 7.10.1Fixed in 8.1.4
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.11.1
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 7.10.1
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.1.4
  9. Upgrade

    Upgrade alpine/c-ares to a version that resolves this vulnerability.

    Fixed in 1.12.0-r1
  10. Upgrade

    Upgrade alpine/nodejs to a version that resolves this vulnerability.

    Fixed in 6.11.1-r0
  11. Upgrade

    Upgrade alpine/nodejs to a version that resolves this vulnerability.

    Fixed in 6.7.0-r1
  12. Upgrade

    Upgrade alpine/nodejs to a version that resolves this vulnerability.

    Fixed in 6.9.5-r1
  13. Upgrade

    Upgrade alpine/nodejs to a version that resolves this vulnerability.

    Fixed in 6.10.3-r1
  14. Upgrade

    Upgrade alpine/nodejs-current to a version that resolves this vulnerability.

    Fixed in 7.10.1-r0

Event History

Jul 7, 2017
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Data Sourced
via NVD·05:29 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·05:29 PM
DescriptionSeverityAffected Software
Jul 11, 2017
Data Sourced
via Node.js·04:53 PM
SeverityAffected Software
Jan 3, 2025
Advisory Published
via F5·05:50 PM
Data Sourced
via F5·05:50 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2017-1000381?

CVE-2017-1000381 has a medium severity rating due to the potential for memory exposure.

2

How do I fix CVE-2017-1000381?

To fix CVE-2017-1000381, update affected F5 BIG-IP and c-ares software to the latest patched versions.

3

What products are affected by CVE-2017-1000381?

CVE-2017-1000381 affects specific versions of F5 BIG-IP and c-ares, particularly versions 1.8.0 through 1.12.0 of c-ares.

4

What are the potential impacts of CVE-2017-1000381?

The potential impacts of CVE-2017-1000381 include unauthorized memory access and possible exploitation if a crafted DNS response is processed.

5

Is CVE-2017-1000381 actively being exploited?

As of the last known reports, there is no evidence that CVE-2017-1000381 is actively being exploited in the wild.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203