CVE-2024-22248
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 · uneditedVMware SD-WAN Orchestrator contains an open redirect vulnerability. A malicious actor may be able to redirect a victim to an attacker controlled domain due to improper path handling leading to sensitive information disclosure.
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 confidenceVMware SD-WAN Orchestrator contains an open redirect vulnerability caused by improper path handling. An attacker can craft malicious URLs to redirect authenticated users to attacker-controlled domains, potentially leading to credential theft or session hijacking via phishing.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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.
-
Confirm VMware SD-WAN Orchestrator is presentCheck running services or installed applications for 'VMware SD-WAN Orchestrator' or 'Velocloud Orchestrator'Affected if The product is not installed or running, then the environment is not affected
-
Identify the installed versionAccess the Orchestrator web interface and navigate to the about or system info page, or check the installation directory for version manifest filesAffected if The installed version is older than the vendor-fixed version for CVE-2024-22248, indicating the patch has not been applied
-
Verify the web management interface is accessibleConfirm the Orchestrator web UI is reachable on its configured port (typically 443 or 8443)Affected if The web interface is exposed and the version is unpatched, then exploitation is possible
-
Check for URL redirect functionalityReview the Orchestrator configuration or observe HTTP responses for redirect headers (Location header in 3xx responses)Affected if Redirect functionality is present and the version is unpatched, the open redirect vulnerability exists
-
Determine if URL allowlisting is configuredInspect application configuration or WAF rules for redirect destination allowlists that restrict to trusted domains onlyAffected if No URL allowlisting is implemented and the version is unpatched, the vulnerability is fully exposed to exploitation
If VMware SD-WAN Orchestrator is running with a version prior to the vendor patch and has its web interface accessible without URL redirect allowlisting, the environment is affected by CVE-2024-22248.
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 the vendor-supplied patch for CVE-2024-22248. As an interim control, implement URL validation and allowlisting at the application or WAF layer to restrict redirects to trusted domains only.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22248 — 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-22248 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