dbcve.org
JodfApplication · Independentsoft

CVE-2023-28150

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-24
Fix available
A fix is available. Upgrade to 1.1.110 or later.
See remediation →
100/100
Remediation priority · Urgent
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
An issue was discovered in Independentsoft JODF before 1.1.110. The API is prone to XML external entity (XXE) injection via a remote DTD in a DOCX file.

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

Independentsoft JODF versions prior to 1.1.110 contain a vulnerable XML parser that processes external entities from remote DTDs without proper validation. When parsing DOCX files (which are ZIP archives containing XML), an attacker can embed malicious external entity references that cause the parser to fetch remote resources, potentially leading to disclosure of local files or server-side request forgery.

MitigationUpgrade Independentsoft JODF to version 1.1.110 or later. If upgrade is not immediately feasible, configure the XML parser to disable external entity processing and DTD processing.

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
JodfApplication
Affected:< 1.1.110

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

CVSS:3.1/AV:N/AC:L/PR:N/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 JODF library presence
    Search your project dependencies (Maven pom.xml, Gradle build.gradle, NuGet packages.config, or JAR files) for 'independentsoft' or 'jodf' and note the version number listed.
    Affected if The library is present and the version is below 1.1.110.
  2. Verify the exact JODF version in use
    Check your dependency management file or the actual JAR/file version present in your application's classpath or lib folder. Compare against the affected range: any version prior to 1.1.110.
    Affected if The discovered version is less than 1.1.110.
  3. Confirm DOCX parsing functionality is used
    Review your application code for imports of 'Independentsoft' packages and usage of classes such as Document, TextDocument, or any class that reads or parses DOCX files. Look for calls to parsing methods on .docx file inputs.
    Affected if Your application uses JODF to parse DOCX files.
  4. Check XML parser configuration for external entities
    Inspect your application code or configuration for XML parser settings. Look for whether the XMLReader or DocumentBuilderFactory has disabled external entities (setFeature 'http://xml.org/sax/features/external-general-entities' and 'http://xml.org/sax/features/external-parameter-entities' to false) and disabled DTD processing. If using SAXParserFactory, check if setFeature for DTD is disabled.
    Affected if External entity processing or DTD processing is enabled (not explicitly disabled).

You are affected if Independentsoft JODF version below 1.1.110 is in use and your application parses DOCX files using JODF with external entity processing enabled in the XML parser.

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 1.1.110 or later
Fixed in 1.1.110
Interim mitigation

Upgrade Independentsoft JODF to version 1.1.110 or later. If upgrade is not immediately feasible, configure the XML parser to disable external entity processing and DTD processing.

Recommended fix High confidence

1.1.110

  1. Identify the build tool used in your project (Maven, Gradle, or direct JAR dependency)
  2. If using Maven, update the dependency in pom.xml: change version of com independentsoft to 1.1.110
  3. If using Gradle, update the dependency in build.gradle: change version to '1.1.110'
  4. If using direct JAR files, replace the existing jodf library JAR with version 1.1.110 from www.independentsoft.de
  5. Rebuild the project and run all tests to verify functionality
  6. Re-scan or re-test to confirm the XXE vulnerability is remediated

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

Fix this in Jodf Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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