dbcve.org
Wyse Management SuiteApplication · Dell

CVE-2022-46675

MEDIUM · 5.3 CVSS v3.1 Published 2023-02-11
Fix available
A fix is available. Upgrade to after 3.8 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Wyse Management Suite Repository 3.8 and below contain an information disclosure vulnerability. A unauthenticated attacker could potentially discover the internal structure of the application and its components and use this information for further vulnerability research.

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

Wyse Management Suite Repository versions 3.8 and below contain an unauthenticated information disclosure vulnerability. Attackers can discover the internal structure and components of the application through the repository interface without any authentication, potentially aiding further vulnerability research.

MitigationApply available vendor patches for Wyse Management Suite Repository to version 3.8.1 or later, or implement network-level access controls to restrict unauthenticated access to repository endpoints.

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
Wyse Management SuiteApplication
Affected:<= 3.8

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
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify Wyse Management Suite version
    Locate the installed version through the admin console, installation logs, or by querying the application banner/service information. On Windows, check 'Programs and Features' or the installation directory for version files. On Linux, check the RPM/DEB package or installation logs.
    Affected if The installed version is 3.8 or lower (any version up to and including 3.8).
  2. Confirm Repository component is installed
    Verify that the Repository component of Wyse Management Suite is deployed. Check the application architecture or admin panel to confirm Repository services are running. Look for repository-specific services, directories, or web endpoints.
    Affected if The Repository component is present and running as part of the Wyse Management Suite deployment.
  3. Assess network exposure of Repository endpoints
    Determine if the Repository web interface is accessible from untrusted networks. Test connectivity to common repository paths such as /repository, /api/repository, or the main application URL on ports 80/443. Review firewall rules, load balancer configurations, or reverse proxy settings that govern access.
    Affected if The Repository interface is reachable from network segments that contain untrusted or anonymous users without requiring authentication.
  4. Test unauthenticated access to repository paths
    Send HTTP GET requests to repository endpoints without providing any authentication credentials. Common paths to test include the root URL of the WMS application, /repository, /api/v1/repository, or paths revealing internal structure, component listings, or configuration files.
    Affected if HTTP responses return sensitive information about the application structure, components, file listings, or configuration details without any authentication tokens or credentials being supplied.

The environment is affected if Wyse Management Suite version 3.8 or lower is installed, the Repository component is present, and the repository interface is accessible from untrusted networks without authentication.

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
Upgrade available Upgrade to a release after 3.8
Interim mitigation

Apply available vendor patches for Wyse Management Suite Repository to version 3.8.1 or later, or implement network-level access controls to restrict unauthenticated access to repository endpoints.

Recommended fix Moderate confidence

Wyse Management Suite 3.8.1 or later (check Dell support for exact latest stable release)

  1. Identify the current Wyse Management Suite version in use
  2. Access Dell support at www.dell.com and search for Wyse Management Suite security patches or updates
  3. Download and apply the latest Wyse Management Suite version (3.8.1 or later) following Dell's upgrade documentation
  4. Verify the fix by confirming the updated version is > 3.8
Caveat Review Dell's upgrade guide for any migration requirements or prerequisites before updating

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

Fix this in Wyse Management Suite Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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