CVE-2024-22348
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 DevOps Velocity 5.0.0 and IBM UrbanCode Velocity 4.0.0 through 4.0. 25 uses Cross-Origin Resource Sharing (CORS) which could allow an attacker to carry out privileged actions and retrieve sensitive information as the domain name is not being limited to only trusted domains.
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 DevOps Velocity 5.0.0 and UrbanCode Velocity 4.0.0-4.0.25 have a CORS misconfiguration where the Access-Control-Allow-Origin header does not restrict requests to trusted domains only. This allows malicious websites to make authenticated cross-origin requests on behalf of users, potentially executing privileged actions and exfiltrating sensitive data.
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= 5.0.0>= 4.0.0, <= 4.0.15CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 product versionLocate the version information for IBM DevOps Velocity or UrbanCode Velocity. This is typically available in the product's About page, installation directory, or version manifest file (often found in /opt/velocity, /opt/urbancode/velocity, or similar installation paths depending on your deployment).Affected if The installed version is IBM DevOps Velocity 5.0.0 OR UrbanCode Velocity version 4.0.0 through 4.0.15 inclusive.
-
Locate CORS configuration filesIdentify the configuration files that control CORS settings for the application. This may include server configuration files (such as server.xml for WebSphere, httpd.conf for Apache, or nginx.conf for Nginx), application properties files, or the ibm-web-ext.xml file commonly used in IBM WebSphere applications.Affected if You cannot locate any CORS configuration files for the product.
-
Inspect allowed origin settingsOpen the identified CORS configuration files and search for directives related to allowed origins, such as 'Access-Control-Allow-Origin', 'allowedOrigins', 'cors.allowed.origins', or similar CORS headers and parameters. Examine whether the value is set to a wildcard (*), left empty, or contains multiple unrestricted domains.Affected if The CORS allowed origin is set to '*' (asterisk/wildcard) or is not explicitly restricted to a specific list of trusted domain names.
-
Verify origin validation behaviorIf accessible, send a test cross-origin HTTP request with an arbitrary Origin header (such as 'http://malicious-site.com') to the application's API endpoints and examine whether the response includes the Access-Control-Allow-Origin header reflecting the arbitrary origin or a wildcard.Affected if The application returns the arbitrary or wildcard origin in Access-Control-Allow-Origin headers, confirming unrestricted CORS access.
-
Check for trusted origin whitelistReview the CORS configuration to determine if a whitelist of specific trusted domain origins is defined. Look for explicit lists of approved domains rather than open or wildcard configurations.Affected if No explicit whitelist of trusted domain origins exists in the CORS configuration, or the whitelist includes untrusted or unknown domains.
Your environment is affected if the installed product version falls within 5.0.0 (DevOps Velocity) or 4.0.0-4.0.15 (UrbanCode Velocity) AND the CORS configuration allows unrestricted origins (wildcard '*' or any origin) rather than explicitly whitelisting only trusted domains.
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 CORS policy to explicitly whitelist only trusted domain origins in the Access-Control-Allow-Origin header, avoiding wildcard (*) values, and validate all cross-origin requests server-side.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22348 — 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-22348 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