CVE-2024-28778
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 Cognos Controller 11.0.0 through 11.0.1 and IBM Controller 11.1.0 is vulnerable to exposure of Artifactory API keys. This vulnerability allows users to publish code to private packages or repositories under the name of the organization.
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 Cognos Controller versions 11.0.0 through 11.0.1 and 11.1.0 contain exposed Artifactory API keys in configuration or storage. This allows authenticated users with access to the keys to publish packages to private Artifactory repositories under the organization's identity, potentially leading to supply chain compromise or unauthorized code distribution.
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.0.0, <= 11.0.1= 11.1.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Cognos Controller versionOpen Windows Programs and Features or check the application about/help section for the exact version numberAffected if Version is 11.0.0, 11.0.1, or 11.1.0 (vulnerable versions)
-
Locate Artifactory configuration filesSearch the IBM Cognos Controller installation directory and configuration folders for files named something like 'artifactory.properties', 'artifactory.config', or XML/YAML files containing Artifactory settingsAffected if Artifactory configuration files exist and contain stored API keys or credentials
-
Inspect database storage for exposed credentialsExamine the IBM Cognos Controller database or configuration storage tables/entries for Artifactory API keys stored in plaintext or weakly encrypted formAffected if API keys or credentials for Artifactory are found stored in configuration or database
-
Verify Artifactory integration is enabledCheck the Cognos Controller administration or integration settings to determine if Artifactory connectivity is configured and activeAffected if Artifactory integration is configured and operational in the environment
You are affected if running Cognos Controller version 11.0.0 through 11.0.1 or 11.1.0 AND Artifactory integration has been configured with API keys stored in the product's configuration or storage.
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 dataImmediately rotate any Artifactory API keys that may have been exposed in IBM Cognos Controller configurations. Review Artifactory access logs for unauthorized package publications and upgrade to patched versions when available.
- Consultation4.0 h
- Implementation6.0 h
- Testing2.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28778 — 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-28778 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