CVE-2019-13617 Memory corruption in n/a

Medium 6.5 Published Updated

A heap-based buffer over-read in the njs library used by NGINX allows attackers to cause denial of service or disclose sensitive memory contents.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2019-13617?

CVE-2019-13617 is a medium-severity memory corruption vulnerability in n/a, published on 16 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

njs through 0.3.3, used in NGINX, has a heap-based buffer over-read in nxt_vsprintf in nxt/nxt_sprintf.c during error handling, as demonstrated by an njs_regexp_literal call that leads to an njs_parser_lexer_error call and then an njs_parser_scope_error call.

Weakness: CWE-125

Which versions are affected by CVE-2019-13617?

It affects 1 product.

Products include F5 Njs.

How do I fix CVE-2019-13617?

No fix has been published for CVE-2019-13617 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2019-13617 being exploited?

There is no known exploitation of CVE-2019-13617 in the wild and no public exploit code.

Sources

Also known as GHSA-qp8g-8mj4-549c.

Is CVE-2019-13617 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free