CVE-2010-2323
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 · uneditedIBM WebSphere Application Server (WAS) 7.0 before 7.0.0.11 on z/OS might allow attackers to obtain sensitive information by reading the default_create.log file that is associated with profile creation by the BBOWWPFx job and the zPMT.
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 confidenceIBM WebSphere Application Server 7.0 before fix pack 11 on z/OS creates a default_create.log file during profile setup (via BBOWWPFx job and zPMT tool) that contains sensitive information. This log file has insufficient access controls, allowing unauthorized users to read it and obtain potentially sensitive data exposed during profile creation.
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.0.10= 7.0= 7.0.0.1= 7.0.0.2= 7.0.0.3= 7.0.0.4= 7.0.0.5= 7.0.0.6= 7.0.0.7= 7.0.0.8= 7.0.0.9CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 WebSphere Application Server versionCheck the installed version of IBM WebSphere Application Server on the z/OS system. This can be done by examining the product installation directory or using the WSADMIN tool to query the version. Look for version 7.0.0.x where x is less than 11.Affected if The installed version is 7.0.0.10 or earlier on z/OS
-
Confirm the operating system is z/OSVerify that the WebSphere Application Server installation is running on z/OS, as this vulnerability only affects the z/OS platform.Affected if The operating system is z/OS and WebSphere 7.0.0.10 or earlier is installed
-
Locate the default_create.log fileSearch for the default_create.log file in the profile setup output directories. On z/OS, this file is created during profile creation via the BBOWWPFx job or zPMT tool. Check common locations such as the profile root directory, job output datasets, or the directory where the profile creation job ran.Affected if The default_create.log file exists in the profile setup area
-
Check file permissions on default_create.logExamine the access permissions on the default_create.log file. On z/OS, this can be done using RACF commands (LISTDSD), USS ls -la commands if the file is in USS, or through the equivalent security product. Verify if unauthorized users have READ access to this file.Affected if The file permissions allow unauthorized or non-privileged users to read the default_create.log file
A user is affected if they are running IBM WebSphere Application Server 7.0.0.10 or earlier on z/OS and the default_create.log file exists with overly permissive access controls that allow unauthorized reading.
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 IBM WebSphere Application Server 7.0.0.11 or later which addresses the improper file permissions on the default_create.log. Alternatively, if upgrading is not immediately feasible, manually restrict file permissions on default_create.log to prevent unauthorized read access.
- Consultation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2323 — 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-2010-2323 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