CVE-2007-6260
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe installation process for Oracle 10g and llg uses accounts with default passwords, which allows remote attackers to obtain login access by connecting to the Listener. NOTE: at the end of the installation, if performed using the Database Configuration Assistant (DBCA), most accounts are disabled or their passwords are changed.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOracle 10g and 11g installations create database accounts with default passwords that remain active until the installation completes via DBCA. Remote attackers can exploit this by connecting to the Oracle Listener service and authenticating using these default credentials to gain unauthorized database access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Oracle Database installationCheck for Oracle software installation by examining ORACLE_HOME environment variable and listing installed Oracle binaries (e.g., lsnrctl, sqlplus in $ORACLE_HOME/bin)Affected if Oracle Database Server binaries are present on the system
-
Determine if DBCA completedQuery DBA_USERS or check for presence of default accounts in SQL*Plus: SELECT username, account_status FROM DBA_USERS WHERE username IN ('SYS','SYSTEM','OUTLN','DIP'); Review whether DBCA configuration finished during installationAffected if Default accounts such as SYS, SYSTEM, OUTLN, or DIP show status as OPEN rather than LOCKED or EXPIRED, indicating DBCA never secured these accounts
-
Identify active default credentialsExecute: SELECT username, account_status, password_versions FROM DBA_USERS WHERE account_status = 'OPEN'; Compare against known default Oracle accounts and their default passwords documented in Oracle documentationAffected if Any default Oracle database accounts remain unlocked with default passwords still active after installation
-
Check Oracle Listener accessibilityRun 'lsnrctl status' to confirm Oracle Listener is running and reachable. Verify network exposure by checking if Listener port (default 1521) is bound to a public interface or exposed externallyAffected if Oracle Listener is running and accessible from network locations where untrusted users could attempt connections with default credentials
A system is affected if Oracle Database is installed with default accounts still unlocked due to incomplete or absent DBCA execution, and the Oracle Listener is network-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataChange default passwords for all Oracle database accounts immediately after installation, or ensure the DBCA configuration assistant completes fully to disable or secure accounts. Implement network access controls on the Oracle Listener port.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-6260 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-6260 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data