OrbitalApplication · Cisco
CVE-2021-34772
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 · uneditedA vulnerability in the web-based management interface of Cisco Orbital could allow an unauthenticated, remote attacker to redirect users to a malicious webpage. This vulnerability is due to improper validation of URL paths in the web-based management interface. An attacker could exploit this vulnerability by persuading a user to click a crafted URL. A successful exploit could allow the attacker to redirect a user to a malicious website. This vulnerability, known as an open redirect attack, is used in phishing attacks to persuade users to visit malicious sites.
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 confidenceOpen redirect vulnerability in Cisco Orbital web-based management interface allows unauthenticated remote attackers to redirect users to malicious websites via crafted URLs due to improper validation of URL paths in the interface.
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
OrbitalApplication
all versionsCVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Identify Cisco Orbital installationCheck system inventory or running services for Cisco Orbital software. Look for processes named 'orbital' or services listening on ports associated with Cisco Orbital (typically HTTPS on port 443).Affected if Cisco Orbital is installed and running in the environment
-
Locate the web management interfaceCheck for web interfaces running on hosts where Cisco Orbital is installed. Common paths include /orbital, /management, or the main IP/hostname of the Orbital server on ports 443 or 8443.Affected if The Cisco Orbital web management interface is accessible on the network
-
Verify all versions are affectedQuery the installed version of Cisco Orbital via software inventory, running service version headers, or management interface 'About' or 'Version' page.Affected if Any version of Cisco Orbital is confirmed to be running (the advisory states all versions are affected)
-
Review access to the management interfaceDetermine if the web management interface is exposed to untrusted networks or the internet. Check firewall rules and network segmentation for ports 443/tcp and 8443/tcp.Affected if The interface is reachable from untrusted networks without VPN or authentication barriers
-
Inspect URL redirect behaviorNavigate to the login page or any authenticated area, then observe whether URL parameters can be manipulated to cause redirects (e.g., ?redirect= or ?url= parameters). Compare behavior against expected internal redirects.Affected if The interface accepts and follows redirects to external domains via URL parameters without validation
If Cisco Orbital is installed with its web management interface accessible, the environment is affected since all versions contain the open redirect vulnerability.
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 Cisco-provided patch for CVE-2021-34772; implement URL validation and allowlist controls for redirect destinations in the web interface.
Fix this in Orbital
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34772 — 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-2021-34772 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