Vulnerability in nodejs (ALPINE-CVE-2021-22918)

Summary

Vulnerability in nodejs (ALPINE-CVE-2021-22918). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 12.22.2-r0 or later.

Original description

The description as published by the source.

Node.js before 16.4.1, 14.17.2, 12.22.2 is vulnerable to an out-of-bounds read when uv__idna_toascii() is used to convert strings to ASCII. The pointer p is read and increased without checking whether it is beyond pe, with the latter holding a pointer to the end of the buffer. This can lead to information disclosures or crashes. This function can be triggered via uv_getaddrinfo().

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as ALPINE-CVE-2021-22918 has been found in nodejs.
Risk of unauthorized operations or information disclosure.
What to do: upgrade nodejs to 12.22.2-r0 or later.
If unsure, ask your IT team or search "nodejs ALPINE-CVE-2021-22918" on the vendor's site.

ALPINE-CVE-2021-22918 (nodejs)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 12.22.2-r0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in nodejs.

📍 Affected scope

Check the vendor advisory for the affected versions of nodejs.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 12.22.2-r0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nodejs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'nodejs' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で nodejs を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade nodejs to 12.22.2-r0
```
ステージング環境で 12.22.2-r0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Alpine:v3.11 nodejs

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.2-r0"}]}]

Alpine:v3.12 nodejs

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.2-r0"}]}]

Alpine:v3.13 nodejs

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.3-r0"}]}]

Alpine:v3.14 nodejs

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.3-r0"}]}]

References

advisory security.alpinelinux.org