CVE-2018-10088

CVE-2018-10088 is a critical-severity vulnerability in Xiongmaitech Uc-httpd with a CVSS 3.x base score of 9.8. Its EPSS exploit-prediction score of 40% places it in the 98th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-119.

Key facts

Description

Buffer overflow in XiongMai uc-httpd 1.0.0 has unspecified impact and attack vectors, a different vulnerability than CVE-2017-16725.

Frequently asked questions

What is CVE-2018-10088?
Buffer overflow in XiongMai uc-httpd 1.0.0 has unspecified impact and attack vectors, a different vulnerability than CVE-2017-16725.
How severe is CVE-2018-10088?
CVE-2018-10088 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2018-10088 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 40% (98th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-10088?
CVE-2018-10088 affects Xiongmaitech Uc-httpd. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-10088?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2018-10088 published?
CVE-2018-10088 was published on 2018-06-08 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Xiongmaitech Uc-httpd

All CVEs affecting Xiongmaitech Uc-httpd →

Other CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities

Browse all CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: