# ALEA-2020:5101: nodejs:14 bug fix and enhancement update

> An update to Node.js 14 provides bug fixes and enhancements, with no specific security vulnerability details provided in the advisory.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 12 Nov 2020

## What is ALEA-2020:5101?

ALEA-2020:5101 is a vulnerability in nodejs-nodemon, published on 12 Nov 2020. 

### Official description

Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.

The following packages have been upgraded to a later upstream version: rh-nodejs14-nodejs (14.15.0). (BZ#1891809)

## Which versions are affected by ALEA-2020:5101?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nodejs-nodemon` | AlmaLinux:8 | All versions | 2.0.3-1.module_el8.4.0+2521+c668cc9f |
| `nodejs-nodemon` | AlmaLinux:8 | All versions | 2.0.3-1.module_el8.5.0+85+79a7b441 |
| `nodejs-packaging` | AlmaLinux:8 | All versions | 23-3.module_el8.4.0+2522+3bd42762 |
| `nodejs-packaging` | AlmaLinux:8 | All versions | 23-3.module_el8.5.0+254+b4526b16 |

## How do I fix ALEA-2020:5101?

Upgrade to a fixed version.

## Is ALEA-2020:5101 being exploited?

There is no known exploitation of ALEA-2020:5101 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALEA-2020:5101 and fix it if it is affected.

What it is: ALEA-2020:5101 is a vulnerability in nodejs-nodemon, published on 12 Nov 2020. 
Exploitation: There is no known exploitation of ALEA-2020:5101 in the wild and no public exploit code.

Affected product: nodejs-nodemon. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/ALEA-2020-5101/ (Markdown: https://insights.sbomify.com/ALEA-2020-5101/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALEA-2020:5101

---
From sbomify Insights: https://insights.sbomify.com/ALEA-2020-5101/
Summaries are generated and may contain mistakes; the official description above is the record.