dbcve.org
Duo Authentication For EpicApplication · Cisco

CVE-2024-20503

MEDIUM · 5.5 CVSS v3.1 Published 2024-09-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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
A vulnerability in Cisco Duo Epic for Hyperdrive could allow an authenticated, local attacker to view sensitive information in cleartext on an affected system. This vulnerability is due to improper storage of an unencrypted registry key. A low-privileged attacker could exploit this vulnerability by viewing or querying the registry key on the affected system. A successful exploit could allow the attacker to view sensitive information in cleartext.

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 vulnerability in Cisco Duo Epic for Hyperdrive allows an authenticated, low-privileged local attacker to view sensitive information in cleartext due to improper storage of an unencrypted registry key. The attacker can read this data by viewing or querying the affected registry key on the Windows system.

MitigationThe vendor should encrypt sensitive data before storing it in the Windows registry to prevent cleartext exposure of credentials or other sensitive information.

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
Duo Authentication For EpicApplication
Affected:= 1.0.0= 1.0.1= 1.1.9= 1.1.10= 1.1.13= 1.2.0.95

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Verify Cisco Duo Authentication For Epic installation and version
    Open Windows Settings > Apps & Features, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Duo*Epic*"}' in PowerShell. Check if the version matches any of these: 1.0.0, 1.0.1, 1.1.9, 1.1.10, 1.1.13, or 1.2.0.95
    Affected if The installed version is one of the listed affected versions (1.0.0, 1.0.1, 1.1.9, 1.1.10, 1.1.13, or 1.2.0.95)
  2. Locate the Cisco Duo Epic registry key
    Open Registry Editor (regedit.exe) and search for registry keys containing 'Duo' and 'Epic' or 'Hyperdrive' under HKEY_LOCAL_MACHINE\SOFTWARE or HKEY_CURRENT_USER\SOFTWARE. Common paths include keys under the Cisco or Duo product subfolders.
    Affected if A registry key associated with Cisco Duo Epic for Hyperdrive exists on the system
  3. Inspect registry key for cleartext sensitive data
    Right-click the identified registry key and select 'Export' or view the data values. Look for any of the following stored in plaintext: passwords, API keys, tokens, shared secrets, or credential strings. Query via command line: reg query "<registry_path>" /v *
    Affected if The registry key contains passwords, API keys, tokens, or other sensitive values stored in readable, unencrypted plaintext format
  4. Verify if authentication credentials are exposed
    Examine the data values within the registry key for patterns matching credentials: look for fields labeled 'Password', 'Secret', 'Key', 'Token', 'Auth', or similar. Check if these fields contain actual credential strings rather than encrypted or hashed values.
    Affected if Credential or secret values are present in cleartext within the registry key data

You are affected if Cisco Duo Authentication For Epic version 1.0.0, 1.0.1, 1.1.9, 1.1.10, 1.1.13, or 1.2.0.95 is installed AND unencrypted sensitive information (credentials, keys, tokens) is found stored in cleartext within the affected registry key.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

The vendor should encrypt sensitive data before storing it in the Windows registry to prevent cleartext exposure of credentials or other sensitive information.

Fix this in Duo Authentication For Epic Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20503 — 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-2024-20503 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