dbcve.org
Bea Product SuiteApplication · Oracle

CVE-2009-1012

HIGH · 10.0 CVSS v2.0 Published 2009-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 plug-ins for Apache and IIS web servers in Oracle BEA WebLogic Server 7.0 Gold through SP7, 8.1 Gold through SP6, 9.0, 9.1, 9.2 Gold through MP3, 10.0 Gold through MP1, and 10.3 allows remote attackers to affect confidentiality, integrity, and availability. NOTE: the previous information was obtained from the April 2009 CPU. Oracle has not commented on claims from a reliable researcher that this is an integer overflow in an unspecified plug-in that parses HTTP requests, which leads to a heap-based buffer overflow.

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 confidence

Integer overflow vulnerability in Apache and IIS web server plug-ins for Oracle BEA WebLogic Server allows heap-based buffer overflow via crafted HTTP request parsing, enabling remote code execution with CVSS 10 severity.

MitigationApply Oracle Critical Patch Update April 2009 or later. For end-of-life versions (7.0, 8.1, 9.x), upgrade to a supported WebLogic Server version and ensure web server plug-ins are updated accordingly.

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
Bea Product SuiteApplication
Affected:= 7.0= 8.1= 9.0= 9.1= 9.2= 10.0= 10.3

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Oracle WebLogic Server is installed
    Check for WebLogic installation directories (e.g., BEA_HOME, Oracle/Middleware/weblogic), look for weblogic.Server process running, or check for WebLogic-specific files in common installation paths
    Affected if WebLogic Server is present on the system
  2. Determine the WebLogic Server version
    Check the version file in the installation directory (typically in the registry or version info), or run 'java -jar weblogic.jar' from the installation, or check the 'registry.xml' file under the BEA/Oracle home directory
    Affected if Version is 7.0, 8.1, 9.0, 9.1, 9.2, 10.0, or 10.3
  3. Confirm web server plug-in installation
    Inspect the web server (Apache or IIS) configuration for WebLogic plug-in modules: for Apache check httpd.conf or loaded modules for 'mod_weblogic' or 'mod_wl' entries; for IIS check ISAPI filter or script map entries pointing to 'wlisapi' or 'nsapi' redirectors
    Affected if Apache or IIS web server plug-ins for WebLogic are configured and loaded
  4. Verify plug-in version matches vulnerable release
    Check the plug-in DLL/shared library version file (e.g., 'mod_wl_22.so' or 'wlisa.dll') in the web server module directory, or view version information via file properties; for Apache also check the 'WL_HOME' or 'BEA_HOME' plug-in directory for version manifests
    Affected if Plug-in version corresponds to the vulnerable WebLogic versions listed (7.0 through 10.3)

Your environment is affected if WebLogic Server versions 7.0-10.3 are installed AND Apache or IIS web server plug-ins for WebLogic are configured, as the integer overflow vulnerability exists specifically in these plug-ins when handling HTTP requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update April 2009 or later. For end-of-life versions (7.0, 8.1, 9.x), upgrade to a supported WebLogic Server version and ensure web server plug-ins are updated accordingly.

Recommended fix Moderate confidence

For long-term fix, upgrade to WebLogic 10.3.6 or later which includes all historical security patches

  1. Apply Oracle Critical Patch Update (CPU) April 2009, which addresses this vulnerability in the Apache and IIS WebLogic plug-ins.
  2. Download the appropriate patch for your WebLogic version (7.0 SP7, 8.1 SP6, 9.0, 9.1, 9.2 MP3, 10.0 MP1, or 10.3) from Oracle Support.
  3. Before applying the patch, back up your current WebLogic installation and configuration.
  4. Apply the patch following Oracle's standard patch application procedures using OPatch or the native installer.
  5. Restart the WebLogic Server and affected web servers (Apache/IIS) to ensure the patched plug-in is loaded.
  6. Verify the patch was applied successfully by checking the WebLogic version and patch inventory.
Caveat Major version upgrades may require application compatibility testing; legacy plug-in configurations may need adjustment

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

Fix this in Bea Product Suite Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2009-1012 — 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-2009-1012 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