dbcve.org
Weblogic ServerApplication · Oracle

CVE-2010-0073

HIGH · 10.0 CVSS v2.0 Published 2010-04-14
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
Unspecified vulnerability in the WebLogic Server in Oracle WebLogic Server 7.0 SP7, 8.1 SP6, 9.0, 9.1, 9.2 MP3, 10.0 MP2, and 10.3.2 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors.

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

A detailed technical summary for this CVE is being prepared.

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
Weblogic ServerApplication
Affected:= 7.0= 8.1= 9.0= 9.1= 9.2= 10.0= 10.3.2.0.0

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Recommended fix Moderate confidence

Apply vendor patch from Oracle Critical Patch Update; for upgrade path, move to WebLogic 10.3.3 or later which contains the security fix

  1. Apply the Oracle Critical Patch Update that addresses CVE-2010-0073. Refer to the vendor advisory at http://www.oracle.com/technology/deploy/security/alerts/alert-cve-2010-0073.html for the specific patch applicable to your WebLogic Server version.
  2. For WebLogic Server 7.0, apply SP7 (7.0 SP7) or later which contains the security fix.
  3. For WebLogic Server 8.1, apply SP6 (8.1 SP6) or later which contains the security fix.
  4. For WebLogic Server 9.0 and 9.1, apply the appropriate patch from Oracle's vendor advisory.
  5. After applying the patch, restart all WebLogic Server instances and managed servers.
  6. Verify the patch was applied successfully by checking the WebLogic Server version and confirming the vulnerability is resolved through testing.
Caveat Patches may require downtime for WebLogic Server restart; test thoroughly in non-production environment before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0073 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-0073 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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