Application Automation ToolsApplication · Microfocus
CVE-2024-4189
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 · uneditedImproper Restriction of XML External Entity Reference vulnerability in OpenText Application Automation Tools allows DTD Injection.This issue affects OpenText Application Automation Tools: 24.1.0 and below.
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 confidenceThis is an XML External Entity (XXE) vulnerability, specifically a DTD Injection flaw in OpenText Application Automation Tools version 24.1.0 and below. The application fails to properly restrict XML external entity references, allowing attackers to inject malicious DTD (Document Type Definition) content into XML inputs. This can lead to disclosure of local files, denial of service, or server-side request forgery (SSRF) 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
Application Automation ToolsApplication
<= 24.1.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Application Automation Tools is installedLocate the OpenText or Microfocus Application Automation Tools installation directory. Common paths include /opt/microfocus/ or C:\Program Files\Microfocus\. Check for directories named 'Application Automation Tools' or 'aat'.Affected if The product is present on the system
-
Check installed versionLook for a version file or check the product's 'about' information within the application. Common locations: VERSION file in the install directory, or look for version information in the application configuration files.Affected if Installed version is 24.1.0 or any version below 24.1.0
-
Identify XML processing componentsReview application configuration files (XML, YAML, properties files) for XML parsers or handlers. Look for configurations related to XML import, XML upload, or XML-based test execution features.Affected if XML processing components are present and configured for use
-
Check XML parser configuration for DTD/external entity processingExamine XML parser settings in configuration files or Java application configurations (web.xml, spring configs, etc.). Look for settings like 'external-general-entities', 'external-parameter-entities', or 'allow-dtd-processing'.Affected if DTD processing is enabled or external entity settings are not explicitly disabled
-
Verify XML input validationReview application logs or test configurations for XML input paths. Check if there are validation filters or schemas applied to incoming XML data.Affected if XML inputs are accepted without sanitization or schema validation
The environment is affected if Application Automation Tools version 24.1.0 or below is installed AND the application processes XML inputs with DTD/external entity processing enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataDisable external entity processing and DTD parsing in XML handlers throughout the application. Apply vendor-provided patches when available and validate/sanitize all XML input before processing.
Fix this in Application Automation Tools
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-4189 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-4189 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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