Sign inStart freeBook a demo

What is CVE-2022-41742?A high-severity flaw in Nginx, explained.

High severity4 affected products
The short answer

CVE-2022-41742 is a high-severity flaw (CVSS 7.1) in Nginx from F5, published on 19 October 2022. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 1.2%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 19 October 2022. Record last updated 7 November 2023. We keep this page's data up to date.

What it does

What is CVE-2022-41742? In plain terms.

An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data and take it offline.

The official description

NGINX Open Source before versions 1.23.2 and 1.22.1, NGINX Open Source Subscription before versions R2 P1 and R1 P1, and NGINX Plus before versions R27 P1 and R26 P1 have a vulnerability in the module ngx_http_mp4_module that might allow a local attacker to cause a worker process crash, or might result in worker process memory disclosure by using a specially crafted audio or video file. The issue affects only NGINX products that are built with the module ngx_http_mp4_module, when the mp4 directive is used in the configuration file. Further, the attack is possible only if an attacker can trigger processing of a specially crafted audio or video file with the module ngx_http_mp4_module.

What kind of flaw is it?

  • CWE-787Out-of-bounds Write
CVSS 3.1 scoreHigh · 7.1

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAlready on the device
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstAn ordinary user account
  • Does someone have to clickNo, nobody has to do anything
  • What an attacker getsCan read data and take it offline

Severity vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Exploitation

Is CVE-2022-41742 being exploited? Not that we know of.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.2%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days1.2%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
How Precursor Intelligence ranks it
46out of 100Medium

CVE-2022-41742 scores 46. Action: Plan remediation.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isSmaller factor
  • Threat activity around itSmaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2022-41742 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2022-41742? 4 products.

The published record lists 4 products from 3 vendors. If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2022-41742? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

References

7 links
Precursor Intelligence

Does CVE-2022-41742 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2022-41742 is a high-severity flaw in Nginx from F5, published on 19 October 2022. An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data and take it offline.

It scores 7.1 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2022-41742 is 46 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.2%. That can change at any time, which is why we keep watching.

For Nginx from F5: r1, r2, r22 to r27, 1.1.3 to 1.22.0, 1.23.0, 1.23.1. The record lists 4 products in all, each with its versions, under "Who is affected" on this page.

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

Keep exploring