# ALBA-2019:4275: nodejs:12 bug fix update

> Node.js 12 packages were upgraded to a later upstream version; Node.js users should update.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** Yes
- **Published:** 17 Dec 2019

## What is ALBA-2019:4275?

ALBA-2019:4275 is an other vulnerability in nodejs-nodemon, published on 17 Dec 2019. 

### Official description

The following packages have been upgraded to a later upstream version: nodejs (12.13.1). (BZ#1776116)

## Which versions are affected by ALBA-2019:4275?

An affected version is exposed as installed. No special setting or call is needed.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nodejs-nodemon` | AlmaLinux:8 | All versions | 1.18.3-1.module_el8.3.0+2023+d2377ea3 |
| `nodejs-nodemon` | AlmaLinux:8 | All versions | 1.18.3-1.module_el8.4.0+2224+b07ac28e |
| `nodejs-nodemon` | AlmaLinux:8 | All versions | 1.18.3-1.module_el8.5.0+81+7dbe79d3 |
| `nodejs-packaging` | AlmaLinux:8 | All versions | 17-3.module_el8.3.0+2023+d2377ea3 |
| `nodejs-packaging` | AlmaLinux:8 | All versions | 17-3.module_el8.4.0+2224+b07ac28e |
| `nodejs-packaging` | AlmaLinux:8 | All versions | 17-3.module_el8.5.0+85+79a7b441 |

## How do I fix ALBA-2019:4275?

Upgrade to a fixed version.

## Is ALBA-2019:4275 being exploited?

There is no known exploitation of ALBA-2019:4275 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALBA-2019:4275 and fix it if it is affected.

What it is: ALBA-2019:4275 is an other vulnerability in nodejs-nodemon, published on 17 Dec 2019. 
Exploitation: There is no known exploitation of ALBA-2019:4275 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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/ALBA-2019-4275/ (Markdown: https://insights.sbomify.com/ALBA-2019-4275/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2019:4275

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