Vulnerability in nokogiri (CVE-2019-11068, CVSS 9.8)

Summary

Vulnerability in nokogiri (CVE-2019-11068). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.10.3 or later.

Original description

The description as published by the source.

libxslt through 1.1.33 allows bypass of a protection mechanism because callers of xsltCheckRead and xsltCheckWrite permit access even upon receiving a -1 error code. xsltCheckRead can return -1 for a crafted URL that is not actually invalid and is subsequently loaded.

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-11068 has been found in nokogiri.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade nokogiri to 1.10.3 or later.
If unsure, ask your IT team or search "nokogiri CVE-2019-11068" on the vendor's site.

CVE-2019-11068 (nokogiri) — CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.10.3 — 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 nokogiri.

📍 Affected scope

Check the vendor advisory for the affected versions of nokogiri.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.10.3.

🛡️ 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.3
```
ステージング環境で 1.10.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
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.3"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

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