dbcve.org
Control CenterApplication · Ibm

CVE-2024-35113

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
IBM Control Center 6.2.1 and 6.3.1 could allow an authenticated user to obtain sensitive information exposed through a directory listing.

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 confidence

IBM Control Center versions 6.2.1 and 6.3.1 contain a directory listing vulnerability that allows authenticated users to access file listings of directories that should not be publicly browsable. This can expose sensitive information such as configuration files, credentials, or internal system files that would otherwise be hidden.

MitigationDisable directory listing on the web server/application server by removingIndexes options or adding index files (e.g., index.html). Review and secure any exposed sensitive files discovered through the listing.

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
Control CenterApplication
Affected:= 6.2.1.0= 6.3.1.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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

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

  1. Identify IBM Control Center installation
    Locate the IBM Control Center installation directory and check for version information files or use the product's version command if available
    Affected if IBM Control Center is installed and running
  2. Check installed version
    Determine the exact version number of the installed IBM Control Center instance
    Affected if The installed version is exactly 6.2.1.0 or 6.3.1.0
  3. Verify web server configuration
    Inspect the web server or application server configuration (such as Apache httpd.conf, IIS web.config, or the embedded server configuration) for directory listing settings such as Options Indexes or similar directives
    Affected if Directory listing (Indexes option) is enabled on web directories serving IBM Control Center content
  4. Test for directory listing exposure
    Attempt to access known subdirectories of the IBM Control Center web application via HTTP request without an index file present, such as accessing a directory path directly
    Affected if The server returns a directory listing instead of a 403 Forbidden or an index file

A system is affected only if IBM Control Center version 6.2.1.0 or 6.3.1.0 is installed AND directory listing is enabled on the web server serving the application.

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

Disable directory listing on the web server/application server by removingIndexes options or adding index files (e.g., index.html). Review and secure any exposed sensitive files discovered through the listing.

Recommended fix Moderate confidence

IBM Control Center 6.2.2.x, 6.3.2.x, or latest supported stable release

  1. 1. Identify the current IBM Control Center version in use (6.2.1.0 or 6.3.1.0).
  2. 2. Contact IBM Support or access the IBM Fix Central portal to obtain the latest security fix for this vulnerability.
  3. 3. Request the specific interim fix (iFix) or upgrade package that addresses CVE-2024-35113.
  4. 4. Before applying the fix, review IBM's release notes and security bulletins for version 6.2.2.x and 6.3.2.x or later.
  5. 5. Schedule a maintenance window and backup the current configuration.
  6. 6. Apply the IBM-provided security fix or upgrade to a patched version.
  7. 7. Verify that directory listings are properly restricted after the fix.
  8. 8. Confirm the vulnerability is resolved by testing that sensitive paths are no longer exposed.
Caveat Review IBM release notes for any configuration or compatibility changes between versions; test in non-production environment first

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

Fix this in Control Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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