NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
💎
💎 RubyGems
Not in CISA KEV
HIGH severity

CVE-2014-4993 — backup-agoddard

HIGH

CVE-2014-4993 is a high-severity (CVSS 7.8) Information Exposure vulnerability in backup-agoddard. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

backup-agoddard and backup_checksum have Information Exposure vulnerability

Published
Updated
Affected
2 pkgs
Patched
See advisory
Exploits
2 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk
0.00%0.34%0.67%1.01%0.1%0.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
💎backup-agoddard💎backup_checksum

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

(1) lib/backup/cli/utility.rb in the backup-agoddard gem 3.0.28 and (2) lib/backup/cli/utility.rb in the backup_checksum gem 3.0.23 for Ruby place credentials on the openssl command line, which allows local users to obtain sensitive information by listing the process.

Affected Packages

2 total
EcosystemPackageVulnerable rangeFix
💎RubyGemsbackup-agoddardall versionsNo fix
💎RubyGemsbackup_checksumall versionsNo fix

Affected Products

2 products · 2 configurations
Application
backup checksumbackup_checksum_project
1 version
3.0.23
Application
backup-agoddardbackup-agoddard_project
1 version
3.0.28
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for backup-agoddard, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    The records we use list no patched version of backup-agoddard for CVE-2014-4993. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

(1) `lib/backup/cli/utility.rb` in the `backup-agoddard` gem 3.0.28 and (2) `lib/backup/cli/utility.rb` in the `backup_checksum` gem 3.0.23 for Ruby place credentials on the openssl command line, which allows local users to obtain sensitive information by listing the process.
O3 Security · Impact-Aware SCA

Is CVE-2014-4993 in your dependencies?

Find it across RubyGems, including transitive dependencies.

CVE-2014-4993: backup Info Disclosure (High 7.8)