dbcve.org
XML External Entity (XXE)Weakness · CWE-611

CVE-2023-49110

HIGH · 7.2 CVSS v3.1 Published 2024-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
When the Kiuwan Local Analyzer uploads the scan results to the Kiuwan SAST web application (either on-premises or cloud/SaaS solution), the transmitted data consists of a ZIP archive containing several files, some of them in the XML file format. During Kiuwan's server-side processing of these XML files, it resolves external XML entities, resulting in a XML external entity injection attack. An attacker with privileges to scan source code within the "Code Security" module is able to extract any files of the operating system with the rights of the application server user and is potentially able to gain sensitive files, such as configuration and passwords. Furthermore, this vulnerability also allows an attacker to initiate connections to internal systems, e.g. for port scans or accessing other internal functions / applications such as the Wildfly admin console of Kiuwan. This issue affects Kiuwan SAST: <master.1808.p685.q13371

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

XML External Entity (XXE) injection vulnerability in Kiuwan SAST where the server processes uploaded XML files from scan results without disabling external entity resolution, allowing authenticated Code Security module users to read arbitrary server files and perform internal network reconnaissance.

MitigationDisable XML external entity resolution in the XML parser configuration on the Kiuwan server and upgrade to the patched version (master.1808.p685.q13371 or later).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 Kiuwan SAST installation
    Locate the Kiuwan installation directory or check running services for Kiuwan components. Common paths include /opt/kiuwan or C:\Program Files\Kiuwan. Check if the application is accessible via browser on typical ports like 8080 or 8443.
    Affected if Kiuwan SAST is installed and running in the environment
  2. Determine installed Kiuwan version
    Check the Kiuwan version by logging into the application and navigating to Help > About, or by inspecting version files in the installation directory such as version.properties, build.info, or a similar version manifest file.
    Affected if The installed version is earlier than master.1808.p685.q13371 (vulnerable versions)
  3. Verify user has Code Security module access
    Log into Kiuwan as a user and navigate to the Code Security module. Check user role permissions in Administration > Users to determine if the account has Code Security or scan upload privileges.
    Affected if User account has Code Security module access and can initiate or upload scan results
  4. Confirm XML parser configuration
    Inspect the XML parser configuration files in the Kiuwan installation directory, typically found in conf/ or config/ folders. Look for XML parser settings such as disabling external entity resolution, DTD processing, or similar XXE protections.
    Affected if External entity resolution is NOT explicitly disabled in the XML parser configuration (XXE protection is missing or disabled)

User is affected if Kiuwan SAST is running a version earlier than master.1808.p685.q13371, they have Code Security module access, and the XML parser has not had external entity resolution disabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable XML external entity resolution in the XML parser configuration on the Kiuwan server and upgrade to the patched version (master.1808.p685.q13371 or later).

Recommended fix High confidence

Kiuwan SAST master.1808.p685.q13371 or later

  1. 1. Identify the current installed version of Kiuwan SAST (on-premises or cloud/SaaS)
  2. 2. Contact Kiuwan vendor to obtain the fixed version (master.1808.p685.q13371 or later)
  3. 3. Schedule a maintenance window for the upgrade
  4. 4. Before upgrading, backup all existing configurations, databases, and scan data
  5. 5. Upgrade Kiuwan SAST to the fixed version that disables external XML entity resolution
  6. 6. Verify the upgrade was successful by checking the application version
  7. 7. Confirm XXE vulnerability is remediated by reviewing Kiuwan release notes or security advisories
  8. 8. Test that normal scan functionality still works after the upgrade
Caveat Review Kiuwan release notes for any changes to scan functionality or configuration requirements in the fixed version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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