dbcve.org
Secure Global DesktopApplication · Oracle

CVE-2021-2248

CRITICAL · 10.0 CVSS v3.1 Published 2021-04-22
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
Vulnerability in the Oracle Secure Global Desktop product of Oracle Virtualization (component: Server). The supported version that is affected is 5.6. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Secure Global Desktop. While the vulnerability is in Oracle Secure Global Desktop, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Oracle Secure Global Desktop.

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 confidence

A critical vulnerability in the Server component of Oracle Secure Global Desktop version 5.6 allows unauthenticated remote attackers to gain complete takeover of the affected system via network access using multiple protocols. The CVSS 10 score indicates trivial exploitability with total confidentiality, integrity, and availability impact.

MitigationApply the Oracle Critical Patch Update that addresses CVE-2021-2248, or upgrade to a patched version of Oracle Secure Global Desktop. Until patched, restrict network exposure and implement additional authentication layers for the Server component.

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
Secure Global DesktopApplication
Affected:= 5.6

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
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Oracle Secure Global Desktop is installed
    Locate the SGD installation directory or check for running processes related to 'sgd' or 'Secure Global Desktop' on the system
    Affected if The software is present on the system
  2. Identify the installed version
    Check the version of Oracle Secure Global Desktop by locating version files or using system inventory tools that report installed Oracle products
    Affected if The installed version is exactly 5.6
  3. Verify the Server component is running
    Identify if the SGD Server component is actively running as a service or daemon on the system
    Affected if The Server component is running and accessible
  4. Determine network exposure of the Server component
    Review network configuration, listening ports, and firewall rules to determine if the SGD Server is exposed to network access
    Affected if The Server component is reachable over the network from untrusted sources
  5. Check for existing authentication controls
    Review the SGD configuration to determine if additional authentication layers beyond default settings are implemented
    Affected if Only default authentication is in place with network exposure

A system is affected if Oracle Secure Global Desktop version 5.6 is installed with the Server component running and exposed to network access without additional authentication controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Interim mitigation

Apply the Oracle Critical Patch Update that addresses CVE-2021-2248, or upgrade to a patched version of Oracle Secure Global Desktop. Until patched, restrict network exposure and implement additional authentication layers for the Server component.

Recommended fix Moderate confidence

Oracle Secure Global Desktop 5.7 or later

  1. 1. Review the Oracle Critical Patch Update advisory for April 2021 at https://www.oracle.com/security-alerts/cpuapr2021.html to locate the specific patch for Secure Global Desktop 5.6
  2. 2. Download and apply the relevant patch from Oracle's support portal using your Oracle Support credentials
  3. 3. Alternatively, upgrade Oracle Secure Global Desktop to version 5.7 or later which contains the security fixes
  4. 4. After applying the patch or upgrade, restart the SGD server services
  5. 5. Verify the installation by checking the SGD version and ensuring all services are running properly
  6. 6. Test critical functionality to confirm the system operates normally after the update
Caveat Review Oracle's upgrade documentation for any configuration or compatibility changes between 5.6 and 5.7

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Secure Global Desktop Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-2248 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-2248 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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