CVE-2024-35119
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 InfoSphere Information Server 11.7 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in a stack trace. This information could be used in further attacks against the system. IBM X-Force ID: 290342.
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 confidenceIBM InfoSphere Information Server 11.7 returns detailed technical error messages including stack traces to users, allowing remote attackers to gain sensitive system information such as file paths, library versions, and internal logic that could aid in further attacks.
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= 11.7CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 IBM InfoSphere Information Server versionLocate the installation directory (typically in /opt/IBM/InformationServer or C:\IBM\InformationServer) and check the version file or use the versionInfo.sh/vbs script in the ASBNode/bin directoryAffected if The installed version is exactly 11.7
-
Check WebSphere application server error handling configurationAccess the WebSphere Application Server admin console (typically port 9443 or 9060) and navigate to Servers > Application Servers > [server_name] > Web container > Custom Properties, or check the server.xml file in the WebSphere config directory for 'propfile.encoding' or error page settingsAffected if Detailed error messages or stack traces are enabled in the application server configuration
-
Inspect custom error page configurationCheck the web.xml deployment descriptor in the installed applications (found in the WAScelldir/node/applications directory or the WAR file WEB-INF/web.xml) for <error-page> mappings and verify they point to generic error pages rather than exposing stack tracesAffected if No custom error pages are configured or error pages expose technical details
-
Test for error message disclosureTrigger a deliberate error condition by submitting malformed input to a known endpoint (such as a DataStage job parameter or XML input) or access a non-existent resource, then capture the HTTP responseAffected if The response contains stack traces, file paths, library versions, or other technical implementation details
You are affected if IBM InfoSphere Information Server version 11.7 is running and the application returns detailed stack traces or technical error messages instead of generic error pages.
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 dataConfigure the application server to disable detailed error messages and stack trace display; implement custom error pages that return generic error responses without exposing technical details.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35119 — 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-2024-35119 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