CVE-2024-28787
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 Security Verify Access 10.0.0 through 10.0.7 and IBM Application Gateway 20.01 through 24.03 could allow a remote attacker to obtain highly sensitive private information or cause a denial of service using a specially crafted HTTP request. IBM X-Force ID: 286584.
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 Security Verify Access versions 10.0.0 through 10.0.7 and IBM Application Gateway versions 20.01 through 24.03 contain a vulnerability that can be exploited via specially crafted HTTP requests, allowing remote attackers to obtain highly sensitive private information or cause denial of service. The CVSS 10 score indicates trivial network exploitation with no authentication required.
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>= 20.01, <= 24.03>= 10.0.0, <= 10.0.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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:H
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 IBM Security Verify Access installationLocate the IBM Security Verify Access installation and determine its version number. This is typically found in the product documentation, installation directory, or by querying the product's administration interface for its version information.Affected if The installed version is between 10.0.0 and 10.0.7 inclusive.
-
Identify IBM Application Gateway installationLocate the IBM Application Gateway installation and determine its version number. Check the product's management console, installation directory, or run the product-specific version command if available.Affected if The installed version is between 20.01 and 24.03 inclusive.
-
Verify HTTP exposureDetermine whether the product's HTTP or HTTPS interfaces are accessible from the network. Check network firewall rules, reverse proxy configurations, or the product's listener settings to confirm exposure.Affected if HTTP/HTTPS listeners are enabled and accessible from untrusted networks.
-
Review HTTP access logsExamine the product's HTTP access logs for unusual or malformed request patterns that may indicate exploitation attempts. Look for requests with unexpected parameters, headers, or encoding.Affected if Suspicious HTTP requests are present in the logs or anomalous access patterns are detected.
A defender is affected if they have IBM Security Verify Access versions 10.0.0-10.0.7 or IBM Application Gateway versions 20.01-24.03 running with exposed HTTP interfaces.
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 dataOrganizations running affected versions should upgrade to the latest available patched version of IBM Security Verify Access and IBM Application Gateway. Until patches are applied, network-level filtering of suspicious HTTP requests may provide temporary mitigation.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28787 — 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-28787 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