CVE-2017-10671

Name: CVE-2017-10671
Creator: NVD / NIST
Published: 2017-06-29T08:29:00.217+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

HIGHCVSS 7.8/10EPSS 1.52%

Last modified Jun 17, 2026

CVE-2017-10671 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. Heap-based Buffer Overflow in the de_dotdot function in libhttpd.c in sthttpd before 2.27.1 allows remote attackers to cause a denial of service (daemon crash) or possibly have unspecified other impact via a crafted filename.. EPSS estimates a 1.52% chance of exploitation in the next 30 days.

Description

Heap-based Buffer Overflow in the de_dotdot function in libhttpd.c in sthttpd before 2.27.1 allows remote attackers to cause a denial of service (daemon crash) or possibly have unspecified other impact via a crafted filename.

Metrics

CVSS 3.1

7.8/10

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS Probability

1.52%

71.4th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-787

Affected Software

Vendor	Product	Versions
Sthttpd Project	Sthttpd	< 2.27.1

References

http://www.openwall.com/lists/oss-security/2017/06/15/9Mailing List, Patch, Third Party Advisory
https://github.com/blueness/sthttpd/commit/c0dc63a49d8605649f1d8e4a96c9b468b0bff660Issue Tracking, Patch, Third Party Advisory
https://github.com/blueness/sthttpd/releases/tag/v2.27.1Issue Tracking, Patch, Third Party Advisory
http://www.openwall.com/lists/oss-security/2017/06/15/9Mailing List, Patch, Third Party Advisory
https://github.com/blueness/sthttpd/commit/c0dc63a49d8605649f1d8e4a96c9b468b0bff660Issue Tracking, Patch, Third Party Advisory
https://github.com/blueness/sthttpd/releases/tag/v2.27.1Issue Tracking, Patch, Third Party Advisory

Timeline

Published: Jun 29, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-10671?

How severe is CVE-2017-10671?

CVE-2017-10671 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 1.52% probability of exploitation in the next 30 days.

How do I fix CVE-2017-10671?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-10671?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST