Vulnerability in libonig (DEBIAN-CVE-2017-9229)

Summary

Vulnerability in libonig (DEBIAN-CVE-2017-9229). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 6.1.3-2 or later.

Original description

The description as published by the source.

An issue was discovered in Oniguruma 6.2.0, as used in Oniguruma-mod in Ruby through 2.4.1 and mbstring in PHP through 7.1.5. A SIGSEGV occurs in left_adjust_char_head() during regular expression compilation. Invalid handling of reg->dmax in forward_search_range() could result in an invalid pointer dereference, normally as an immediate denial-of-service condition.

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 DEBIAN-CVE-2017-9229 has been found in libonig.
Risk of unauthorized operations or information disclosure.
What to do: upgrade libonig to 6.1.3-2 or later.
If unsure, ask your IT team or search "libonig DEBIAN-CVE-2017-9229" on the vendor's site.

DEBIAN-CVE-2017-9229 (libonig)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 6.1.3-2 — 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 libonig.

📍 Affected scope

Check the vendor advisory for the affected versions of libonig.

🔥 Severity

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

🔧 How to fix

Update to 6.1.3-2.

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

Affected packages

Debian:12 libonig

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.3-2"}]}]

Debian:13 libonig

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.3-2"}]}]

Debian:14 libonig

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.3-2"}]}]

References

advisory security-tracker.debian.org