CVE-2024-51463
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 i 7.3, 7.4, and 7.5 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.
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 i versions 7.3, 7.4, and 7.5 contain a server-side request forgery (SSRF) vulnerability. An authenticated attacker can exploit this to send unauthorized requests from the IBM i system to internal or external resources, enabling network enumeration and potential pivoting to internal services that should not be externally accessible.
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.3= 7.4= 7.5CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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.
-
Determine IBM i versionRun command 'DSPSYSVAL QSS1MRI' or use 'WRKSYSVAL' to display system value QSS1MRI, or run 'DSPPTF' to see installed PTFs and system releaseAffected if Version displayed is 7.3, 7.4, or 7.5 exactly (7.3.x, 7.4.x, 7.5.x matches the affected versions)
-
Identify authenticated user accessReview user profiles with special authorities using 'WRKUSRPRF USRPRF(*ALL) OUTPUT(*PRINT)' and examine who has external program execution or HTTP client authoritiesAffected if Multiple user profiles exist with authority to execute programs or scripts that can initiate outbound HTTP requests
-
Check for HTTP client functionalityInspect job logs and network connections for any jobs originating from IBM i making HTTP requests to arbitrary URLs. Use 'NETSTAT' option 3 to review active connectionsAffected if Outbound HTTP/HTTPS connections are observed to internal IP ranges or unexpected external hosts from the IBM i system
-
Review Qshell and PASE environmentsCheck for QSH or PASE utilities that can initiate network requests. Examine '/QOpenSys/usr/bin/' and IFS paths for scripts that may use 'curl', 'wget', or similar utilitiesAffected if Utilities capable of HTTP requests exist and are accessible to standard users
You are affected if your IBM i system runs version 7.3, 7.4, or 7.5 and you have users with authority to trigger HTTP request functionality from the system.
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's security patches (PTFs) for this vulnerability when released. In the interim, implement network segmentation to restrict outbound connections from the IBM i system and review user privileges to limit who can trigger the vulnerable functionality.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.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 $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51463 — 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-51463 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