dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 13 Sep 2024.
Versa DirectorApplication · Versa Networks

CVE-2024-39717

HIGH · 7.2 CVSS v3.1 Published 2024-08-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable 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
The Versa Director GUI provides an option to customize the look and feel of the user interface. This option is only available for a user logged with Provider-Data-Center-Admin or Provider-Data-Center-System-Admin. (Tenant level users do not have this privilege). The “Change Favicon” (Favorite Icon) option can be mis-used to upload a malicious file ending with .png extension to masquerade as image file. This is possible only after a user with Provider-Data-Center-Admin or Provider-Data-Center-System-Admin has successfully authenticated and logged in.

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 confidence

Versa Director GUI's 'Change Favicon' feature allows authenticated Provider-Data-Center-Admin or Provider-Data-Center-System-Admin users to upload files with only .png extension validation, enabling malicious file upload attacks where arbitrary code or content can be disguised as image files.

MitigationImplement robust server-side file validation including magic byte verification, content-type checking, and file header analysis rather than relying solely on file extension; store uploaded files outside the webroot with randomized filenames.

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
Versa DirectorApplication
Affected:= 21.2.2= 21.2.3= 22.1.1= 22.1.2= 22.1.3

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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. Identify installed Versa Director version
    Access the Versa Director GUI and navigate to Administration > System > Software/Hardware info, or run 'vnmsh -v' or 'show system version' CLI command to retrieve the installed software version
    Affected if The installed version is 21.2.2, 21.2.3, 22.1.1, 22.1.2, or 22.1.3
  2. Verify user role permissions
    Check the logged-in user's role by navigating to Administration > Users > User Management in the GUI, or use CLI 'show users' command to see assigned roles
    Affected if The user has Provider-Data-Center-Admin or Provider-Data-Center-System-Admin role assigned
  3. Confirm Change Favicon feature is accessible
    Navigate to Administration > Customize > Appearance or similar GUI path for customizing the login page or dashboard appearance, look for a 'Change Favicon' or favicon upload option
    Affected if The Change Favicon upload feature is present and accessible in the GUI interface
  4. Inspect file upload behavior
    Attempt to upload a file with .png extension but containing non-PNG content (e.g., a text file renamed to .png) through the Change Favicon feature to verify if content validation occurs
    Affected if The system accepts the file based solely on .png extension without validating magic bytes or MIME type

You are affected if your Versa Director version matches 21.2.2, 21.2.3, 22.1.1, 22.1.2, or 22.1.3 and you have users with Provider-Data-Center-Admin or Provider-Data-Center-System-Admin roles who can access the Change Favicon upload feature.

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

Implement robust server-side file validation including magic byte verification, content-type checking, and file header analysis rather than relying solely on file extension; store uploaded files outside the webroot with randomized filenames.

Fix this in Versa Director Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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