dbcve.org
Dryice MyxalyticsApplication · Hcltech

CVE-2023-50341

HIGH · 7.5 CVSS v3.1 Published 2024-01-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
HCL DRYiCE MyXalytics is impacted by Improper Access Control (Obsolete web pages) vulnerability. Discovery of outdated and accessible web pages, reflects a "Missing Access Control" vulnerability, which could lead to inadvertent exposure of sensitive information and/or exposing a vulnerable endpoint.

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

HCL DRYiCE MyXalytics contains obsolete web pages that lack proper access control mechanisms. These outdated pages remain accessible to unauthorized users, potentially exposing sensitive information or providing access to vulnerable endpoints.

MitigationIdentify and remove or properly secure all obsolete web pages, implement appropriate access controls for remaining legacy functionality, and conduct a comprehensive review of the application's URL landscape.

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
Dryice MyxalyticsApplication
Affected:= 5.9= 6.0= 6.1

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed version of MyXalytics
    Locate the HCL DRYiCE MyXalytics installation directory and check the product version information, typically found in version files, about dialog, or installation metadata within the product's root directory
    Affected if The installed version matches 5.9, 6.0, or 6.1
  2. Enumerate web application endpoints
    Review the application's web configuration files, WAR deployment descriptors, or URL mappings to identify all accessible web pages and endpoints served by the application
    Affected if The application exposes web endpoints and obsolete pages are present in the deployment
  3. Identify obsolete or legacy web pages
    Examine the web application structure for deprecated, test, sample, or legacy pages that are no longer actively maintained - look for old filenames, backup files, or known legacy functionality in the web content directories
    Affected if Obsolete web pages exist within the application's web root or deployed content
  4. Test unauthenticated access to web pages
    Attempt to access identified obsolete pages from an unauthenticated browser session or using curl/wget without providing credentials - verify whether the pages load without authentication prompts or redirects
    Affected if Obsolete pages are accessible without authentication or authorization checks
  5. Verify access control configurations
    Inspect the application's security configuration, web.xml, or access control settings to determine whether proper authorization rules are defined for all endpoints including legacy pages
    Affected if No access control restrictions are configured for obsolete endpoints

The environment is affected if HCL DRYiCE MyXalytics version 5.9, 6.0, or 6.1 is installed and obsolete web pages are accessible without proper authentication or authorization 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.

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

Identify and remove or properly secure all obsolete web pages, implement appropriate access controls for remaining legacy functionality, and conduct a comprehensive review of the application's URL landscape.

Fix this in Dryice Myxalytics Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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