CVE-2019-13118 medium CVSS 5.3

Vulnerability in nokogiri (CVE-2019-13118)

Summary

Vulnerability in nokogiri (CVE-2019-13118). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.10.5 or later.

Original description

The description as published by the source.

In numbers.c in libxslt 1.1.33, a type holding grouping characters of an xsl:number instruction was too narrow and an invalid character/length combination could be passed to xsltNumberFormatDecimal, leading to a read of uninitialized stack data.

Source: NIST National Vulnerability Database NVD GitHub Advisory

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 CVE-2019-13118 has been found in nokogiri.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade nokogiri to 1.10.5 or later.
If unsure, ask your IT team or search "nokogiri CVE-2019-13118" on the vendor's site.

CVE-2019-13118 (nokogiri) — CWE-843 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.10.5 — 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 (CWE-843) exists in nokogiri.

📍 Affected scope

Check the vendor advisory for the affected versions of nokogiri.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.10.5.

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

Affected packages

rubygems nokogiri

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.10.5"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Alpine Linux ALPINE-CVE-2019-13118 libxslt Fixed in: 1.1.33-r3
BellSoft Alpaquita BELL-CVE-2019-13118
Debian DEBIAN-CVE-2019-13118 libxslt Fixed in: 1.1.32-2.1
Ubuntu UBUNTU-CVE-2019-13118 libxslt Fixed in: 1.1.28-2ubuntu0.2+esm1