Vulnerability in nokogiri (CVE-2019-13118)

Summary

vulnerability in nokogiri (CVE-2019-13118). Confidential information can be exposed externally. Exploitable via ``numbers.c``. Mitigation: upgrade to `1.10.5` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2019-13118** has been found in nokogiri. Attackers can target a specific entry point like ``numbers.c`` over the network to misuse the product. Confidential information can be exposed externally. 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 Attack surface: `numbers.c` / `xsltNumberFormatDecimal` 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. Attackers reach the vulnerable code path via ``numbers.c`` without authentication.

📍 Affected scope

nokogiri — . Attack surface: `numbers.c` / `xsltNumberFormatDecimal`.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally

🔧 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 (7 steps)

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 し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade nokogiri to 1.10.5
```
ステージング環境で 1.10.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

rubygems nokogiri

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

Vulnerability in nokogiri (CVE-2019-13118)

Summary

AI summary snake-internal / snake-material-v2

Response Actions (7 steps)

Affected packages

References

🍪 About cookies