dbcve.org
Myconnection ServerApplication · Visualware

CVE-2023-42035

MEDIUM · 6.5 CVSS v3.0 Published 2024-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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
Visualware MyConnection Server doIForward XML External Entity Processing Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Visualware MyConnection Server. Authentication is not required to exploit this vulnerability. The specific flaw exists within the doIForward method. Due to the improper restriction of XML External Entity (XXE) references, a crafted document specifying a URI causes the XML parser to access the URI and embed the contents back into the XML document for further processing. An attacker can leverage this vulnerability to disclose information in the context of root. Was ZDI-CAN-21774.

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

Visualware MyConnection Server contains an XXE vulnerability in the doIForward method. The XML parser does not properly restrict external entity references, allowing attackers to craft malicious XML documents containing URIs that the parser will access and embed back into the document. This enables disclosure of sensitive information in the context of root without authentication.

MitigationDisable external entity processing in the XML parser configuration and implement strict input validation for XML documents processed by the doIForward method to prevent XXE attacks.

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
Myconnection ServerApplication
Affected:= 11.3c

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
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

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 Visualware MyConnection Server is installed
    Locate the MyConnection Server installation on the system. Check common installation directories such as C:\Program Files\Visualware\ on Windows or /opt/visualware/ on Linux. Look for executable files or service entries named MyConnection Server.
    Affected if Visualware MyConnection Server is not installed on the system
  2. Verify the installed version is exactly 11.3c
    Retrieve the version number of MyConnection Server from the application itself, version information files in the installation directory, or the Windows Add/Remove Programs list. The affected version is specifically 11.3c.
    Affected if The installed version is anything other than 11.3c (this CVE affects only version 11.3c)
  3. Confirm the doIForward method is exposed
    Identify if the doIForward method is accessible in the deployment. This typically involves checking web service endpoints, servlet configurations, or API mappings within the application configuration files such as web.xml or similar deployment descriptors.
    Affected if The doIForward method is not present or not accessible in the application
  4. Check XML parser configuration for external entity processing
    Examine the XML parser configuration used by the doIForward method. Look for parser settings that control external entity resolution, DTD processing, or entity expansion. This may be in configuration files, code that initializes the XML parser, or application properties.
    Affected if External entity processing is enabled or not explicitly disabled in the XML parser configuration

A system is affected by this CVE only if Visualware MyConnection Server version 11.3c is installed, the doIForward method is accessible, and the XML parser has external entity processing enabled.

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

Disable external entity processing in the XML parser configuration and implement strict input validation for XML documents processed by the doIForward method to prevent XXE attacks.

Fix this in Myconnection Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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