CVE-2005-3641
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 · uneditedOracle Databases running on Windows XP with Simple File Sharing enabled, allows remote attackers to bypass authentication by supplying a valid username.
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 Database running on Windows XP with Simple File Sharing enabled allows remote attackers to bypass authentication by supplying a valid username. The vulnerability exploits how Windows Simple File Sharing handles authentication, allowing an attacker to gain unauthorized database access without proper credentials.
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 data= 7.0.2= 7.0.64= 7.1.3= 7.1.5= 7.3.3= 7.3.4= 8.0.1= 8.0.2= 8.0.3= 8.0.4= 8.0.5= 8.0.5.1= 5.0= 5.0.1.0.0= 5.0.2.0.0= 5.0.2.9.0= enterprise_9.0.4.0= enterprise_10.1.0.2= enterprise_10.1.0.3= enterprise_10.1.0.3.1= enterprise_10.1.0.4= personal_9.0.4.0= personal_10.1.0.2= personal_10.1.0.3= personal_10.1.0.3.1= personal_10.1.0.4= standard_9.0.4.0= standard_10.1.0.2= enterprise_8.0.5.0.0= enterprise_8.0.6.0.0= enterprise_8.0.6.0.1= enterprise_8.1.5.0.0= enterprise_8.1.5.0.2= enterprise_8.1.5.1.0= enterprise_8.1.6.0.0= enterprise_8.1.6.1.0= enterprise_8.1.7.0.0= enterprise_8.1.7.1.0= enterprise_8.1.7.4= standard_8.0.6= enterprise_8.1.7= enterprise_9.0.1= enterprise_9.0.1.4= enterprise_9.0.1.5= enterprise_9.0.1.5_fips= enterprise_9.0.2.4= enterprise_9.0.4= enterprise_9.2.0= enterprise_9.2.0.1= enterprise_9.2.0.2= enterprise_9.2.0.3= enterprise_9.2.0.5CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Identify operating system versionRun 'winmsd' or check System Properties to determine if the OS is Windows XPAffected if OS is Windows XP (the vulnerability only applies to Windows XP with Simple File Sharing)
-
Verify Simple File Sharing statusIn Windows XP, open Control Panel > Folder Options > View tab and check 'Use Simple File Sharing (Recommended)' setting, or inspect registry key HKLM\SYSTEM\CurrentControlSet\Control\Lsm for 'ForceGuest' valueAffected if Simple File Sharing is enabled on Windows XP (this is the attack vector)
-
Determine Oracle Database versionConnect to the database and run 'SELECT * FROM v$VERSION;' or check Oracle inventory files in ORACLE_HOME/oratab or ORACLE_HOME/inventory/ContentsXMLAffected if Installed version matches one of the affected versions listed in the CVE (7.0.2 through 10.1.0.4, various 8i and 9i editions)
-
Confirm database is accessible over networkCheck if Oracle listener (TNS) is configured to accept remote connections by examining listener.ora and checking listener status with 'lsnrctl status'Affected if Oracle listener is running and accepting remote connections on Windows XP (required for remote exploitation)
User is affected if running any of the listed Oracle versions on Windows XP with Simple File Sharing enabled and network access exposed.
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 dataDisable Simple File Sharing on affected Windows XP systems and migrate to supported Windows versions as Windows XP is end-of-life. Apply Oracle database security patches and implement network-level access controls to limit database exposure.
- Consultation4.0 h
- Implementation2.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,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3641 — 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-2005-3641 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