Vulnerability in smallvec (CVE-2019-15554)

Summary

Vulnerability in smallvec (CVE-2019-15554). Successful exploitation can lead to full system takeover. Exploitable via grow. Mitigation: upgrade to 0.6.10 or later.

Original description

The description as published by the source.

Attempting to call grow on a spilled SmallVec with a value less than the current capacity causes corruption of memory allocator data structures.

An attacker that controls the value passed to grow may exploit this flaw to obtain memory contents or gain remote code execution.

Credits to @ehuss for discovering, reporting and fixing the bug.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory 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 CVE-2019-15554 has been found in smallvec.
Attackers can target a specific entry point like grow over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade smallvec to 0.6.10 or later.
If unsure, ask your IT team or search "smallvec CVE-2019-15554" on the vendor's site.

CVE-2019-15554 (smallvec)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: grow
Patched: 0.6.10 — 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 smallvec. Attackers reach the vulnerable code path via grow without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of smallvec. Attack surface: grow.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 0.6.10.

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

Affected packages

crates.io smallvec

[{"type":"SEMVER","events":[{"introduced":"0.6.3"},{"fixed":"0.6.10"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2019-15554 rust-smallvec Fixed in: 0.6.10-1

References

advisory rustsec.org
package crates.io
report github.com