Vulnerability in ruby-rails-assets-underscore
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 UBUNTU-CVE-2026-27601 has been found in ruby-rails-assets-underscore.
Risk of unauthorized operations or information disclosure.
What to do: upgrade ruby-rails-assets-underscore to 1.13.8 or later.
If unsure, ask your IT team or search "ruby-rails-assets-underscore UBUNTU-CVE-2026-27601" on the vendor's site.
UBUNTU-CVE-2026-27601 (ruby-rails-assets-underscore)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.13.8 — 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.
A vulnerability (unclassified) exists in ruby-rails-assets-underscore.
Check the vendor advisory for the affected versions of ruby-rails-assets-underscore.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.13.8.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ruby-rails-assets-underscore' . 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 exposureidentify
grep -r 'ruby-rails-assets-underscore' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ruby-rails-assets-underscoreを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade ruby-rails-assets-underscore to 1.13.8ステージング環境で 1.13.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Ubuntu:18.04:LTS | ruby-rails-assets-underscore |
All versions |
— |
| Ubuntu:20.04:LTS | ruby-rails-assets-underscore |
All versions |
— |
| Ubuntu:22.04:LTS | ruby-rails-assets-underscore |
All versions |
— |
| Ubuntu:24.04:LTS | ruby-rails-assets-underscore |
All versions |
— |
Original description The description as published by the source.
Underscore.js is a utility-belt library for JavaScript. Prior to 1.13.8, the _.flatten and _.isEqual functions use recursion without a depth limit. Under very specific conditions, detailed below, an attacker could exploit this in a Denial of Service (DoS) attack by triggering a stack overflow. Untrusted input must be used to create a recursive datastructure, for example using JSON.parse, with no enforced depth limit. The datastructure thus created must be passed to _.flatten or _.isEqual. In the case of _.flatten, the vulnerability can only be exploited if it is possible for a remote client to prepare a datastructure that consists of arrays at all levels AND if no finite depth limit is passed as the second argument to _.flatten. In the case of _.isEqual, the vulnerability can only be exploited if there exists a code path in which two distinct datastructures that were submitted by the same remote client are compared using _.isEqual. For example, if a client submits data that are stored in a database, and the same client can later submit another datastructure that is then compared to the data that were saved in the database previously, OR if a client submits a single request, but its data are parsed twice, creating two non-identical but equivalent datastructures that are then compared. Exceptions originating from the call to _.flatten or _.isEqual, as a result of a stack overflow, are not being caught. This vulnerability is fixed in 1.13.8.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- report ubuntu.com
- report cve.org
- report github.com
- report github.com
- report github.com