CVE-2009-1977 in the critical feed json
Unspecified vulnerability in the Oracle Secure Backup component in Oracle Secure Backup 10.2.0.3 allows remote attackers to affect confiden…
published 2009-07-14 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1972
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 72.6%
- EPSS 72.6% chance of exploitation in 30 days, percentile 99.4%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
Unspecified vulnerability in the Oracle Secure Backup component in Oracle Secure Backup 10.2.0.3 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors. NOTE: the previous information was obtained from the July 2009 Oracle CPU. Oracle has not commented on claims from an independent researcher that this vulnerability allows attackers to bypass authentication via unknown vectors involving the username parameter and login.php.
Timeline
- Published
- First public exploit (Metasploit auxiliary/admin/oracle/osb_execqr2)
Exploit prediction
72.64% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit auxiliary/admin/oracle/osb_execqr2 Oracle Secure Backup Authentication Bypass/Command Injection Vulnerability metasploit auxiliary, normal rank, 2009-08-18
- EDB-9652 Oracle Secure Backup Server 10.3.0.1.0 - Authentication Bypass / Remote Code Injection remote, 2009-09-14
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
References
-
securityfocus.com
/bid/35672
vdb-entry
-
secunia.com
/advisories/35776
third-party-advisory
- zerodayinitiative.com /advisories/ZDI-09-058/
-
vupen.com
/english/advisories/2009/1900
vdb-entry
-
osvdb.org
/55903
vdb-entry
- oracle.com /technetwork/topics/security/cpujul2009-091332.html
-
securitytracker.com
/id?1022565
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/51761
vdb-entry
Sources
- CVE List CVE-2009-1977
- NVD CVE-2009-1977
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.