CVE-2014-4267
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 · uneditedUnspecified vulnerability in the Oracle WebLogic Server component in Oracle Fusion Middleware 10.0.2.0, 10.3.6.0, 12.1.1.0, and 12.1.2.0 allows remote attackers to affect confidentiality, integrity, and availability via vectors related to WLS Core Components.
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 · moderate confidenceUnspecified vulnerability in Oracle WebLogic Server's WLS Core Components affecting versions 10.0.2.0, 10.3.6.0, 12.1.1.0, and 12.1.2.0. Allows remote attackers to impact confidentiality, integrity, and availability via unknown vectors. The specific technical details of the flaw are not publicly disclosed by Oracle.
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= 10.0.2= 10.3.6= 12.1.1= 12.1.2.0.0CVSS 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.
-
Identify Oracle WebLogic Server installation pathLocate the WebLogic installation directory, typically under Oracle Middleware home (e.g., $ORACLE_HOME/wlserver_10.3 or $ORACLE_HOME/wlserver_12.1)Affected if The installation is found at any Oracle Middleware path containing WebLogic versions 10.x or 12.1.x
-
Determine the exact WebLogic Server version numberCheck the version file in the installation: look for a file named 'version.txt' or 'registry.xml' in the wlserver_XX.X directory, or run the command: java -jar $ORACLE_HOME/wlserver_XX.X/server/lib/weblogic.jar -help 2>&1 | head -20Affected if The reported version matches exactly 10.0.2.0, 10.3.6.0, 12.1.1.0, or 12.1.2.0
-
Verify WLS Core Components are presentConfirm the presence of the WLS Core Components module by checking for the 'weblogic.jar' file in the $ORACLE_HOME/wlserver_XX.X/server/lib/ directoryAffected if The WLS Core Components (weblogic.jar) exist in the affected version directories
-
Confirm WebLogic services are runningCheck if the WebLogic Admin Server or Managed Servers are active by reviewing running Java processes containing 'weblogic.Server' or checking the Admin Console at port 7001 by defaultAffected if WebLogic Server instances are running with the affected versions listed above
A user is affected if their Oracle WebLogic Server installation reports a version number that exactly matches 10.0.2.0, 10.3.6.0, 12.1.1.0, or 12.1.2.0 and the WLS Core Components are present and active.
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 dataApply Oracle Critical Patch Update (CPU) for July 2014 or later, or upgrade to a supported Oracle WebLogic Server version beyond 12.1.2.0 that receives security updates.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-4267 — 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-2014-4267 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