dbcve.org
Electronic Delivery Check SystemApplication · Cals Ed

CVE-2024-21765

MEDIUM · 5.5 CVSS v3.1 Published 2024-01-24
Fix available
A fix is available. Upgrade to 11.0.0 / 13.0.0 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
Electronic Delivery Check System (Doboku) Ver.18.1.0 and earlier, Electronic Delivery Check System (Dentsu) Ver.12.1.0 and earlier, Electronic Delivery Check System (Kikai) Ver.10.1.0 and earlier, and Electronic delivery item Inspection Support SystemVer.4.0.31 and earlier improperly restrict XML external entity references (XXE). By processing a specially crafted XML file, arbitrary files on the system may be read by an attacker.

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

This is an XML External Entity (XXE) injection vulnerability in the Electronic Delivery Check System (multiple variants: Doboku, Dentsu, Kikai) and Inspection Support System. The applications improperly restrict XML external entity references when processing XML files, allowing attackers to read arbitrary files on the system by supplying specially crafted XML with external entity declarations.

MitigationDisable XML external entity processing in the application's XML parser configuration, implement input validation for XML files, and upgrade to versions beyond 18.1.0 (Doboku), 12.1.0 (Dentsu), 10.1.0 (Kikai), and 4.0.31 (Inspection Support System).

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
Electronic Delivery Check SystemApplication
Affected:< 11.0.0< 13.0.0< 19.0.0
Electronic Delivery Item Inspection Support SystemApplication
Affected:<= 4.0.31

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 product variant
    Locate the Cals Ed Electronic Delivery Check System or Inspection Support System installation directory and check for product identification files, logs, or registry entries that indicate the variant (Doboku, Dentsu, Kikai, or Inspection Support System).
    Affected if Any of these four product variants are installed and the version falls within the affected ranges.
  2. Determine installed version
    Check the application's version information through its main executable, about dialog, version file, or installation logs. Compare against affected versions: < 11.0.0, < 13.0.0, < 19.0.0 for Electronic Delivery Check System; <= 4.0.31 for Inspection Support System.
    Affected if The installed version is lower than 11.0.0, 13.0.0, or 19.0.0 for Electronic Delivery Check System, or 4.0.31 or lower for Inspection Support System.
  3. Verify XML file processing is enabled
    Examine the application's configuration files (typically in conf/, config/, or settings/ directories) for XML parser settings. Look for configurations related to DTD processing, external entity resolution, or XML validation that may indicate XXE protection is absent.
    Affected if XML file import or processing features are enabled and the XML parser is configured to allow external entity references (no disabling of XXE vectors).
  4. Inspect XML upload or import functionality
    Review application logs, web interface settings (if web-based), or file handling modules to determine if the application accepts XML files from users. Check for endpoints or functions that process XML uploads.
    Affected if The application accepts XML file uploads or processes XML files from external sources without sanitization.

The environment is affected if a vulnerable variant (Doboku, Dentsu, Kikai, or Inspection Support System) with a version below the fixed releases is installed AND the application processes XML files with external entity support 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
Upgrade available Upgrade to 11.0.0 / 13.0.0 / 19.0.0 or later
Fixed in 11.0.013.0.019.0.0
Interim mitigation

Disable XML external entity processing in the application's XML parser configuration, implement input validation for XML files, and upgrade to versions beyond 18.1.0 (Doboku), 12.1.0 (Dentsu), 10.1.0 (Kikai), and 4.0.31 (Inspection Support System).

Fix this in Electronic Delivery Check System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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