Your RSA-2048 keys break in 2030. Find every one of them before attackers do.

CVE-2019-17268

CRITICAL

CVE-2019-17268 is a critical-severity (CVSS 9.8) Code Injection vulnerability in omniauth-weibo-oauth2_project omniauth-weibo-oauth2. O3 Security detects and blocks CVE-2019-17268 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

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.

Published
Feb 7, 2020
Updated
Jun 17, 2026
Affected
0 pkgs
Patched
None yet
Exploits
None indexed

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.

Affected Products

1 product · 1 configurations
Application
omniauth-weibo-oauth2omniauth-weibo-oauth2_project
1 version
0.4.6

Detection & mitigation playbook

Vendor / appliance
  1. Detect

    Inventory every omniauth-weibo-oauth2_project omniauth-weibo-oauth2 deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

  2. Remediation status

    No patch has shipped for CVE-2019-17268 yet — track the omniauth-weibo-oauth2_project omniauth-weibo-oauth2 advisory for a fixed release and apply the workarounds below in the meantime.

  3. Mitigate without a patch

    Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

  4. How O3 protects you

    O3 detects and blocks CVE-2019-17268 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2019-17268. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Runtime Protection

Is CVE-2019-17268 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2019-17268 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.