CVE-2023-47143
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 · uneditedIBM Tivoli Application Dependency Discovery Manager 7.3.0.0 through 7.3.0.10 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers. This could allow an attacker to conduct various attacks against the vulnerable system, including cross-site scripting, cache poisoning or session hijacking. IBM X-Force ID: 270270.
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 confidenceHTTP header injection vulnerability in IBM Tivoli Application Dependency Discovery Manager versions 7.3.0.0-7.3.0.10 caused by improper validation of HOST header input. Attackers can inject arbitrary HTTP headers leading to cross-site scripting, cache poisoning, or session hijacking.
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>= 7.3.0.0, < 7.3.0.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if IBM Tivoli Application Dependency Discovery Manager is installedLocate the installation directory or check system inventory for IBM Tivoli Application Dependency Discovery Manager softwareAffected if The product is present on the system
-
Determine the installed version of IBM Tivoli Application Dependency Discovery ManagerUse the product's version reporting mechanism, check installation logs, or consult the product's about/version information panel in the administrative consoleAffected if The installed version is 7.3.0.0 through 7.3.0.10 inclusive
-
Compare installed version against affected rangeVerify the exact version number against the vulnerable range: >= 7.3.0.0 and < 7.3.0.11Affected if The version falls within 7.3.0.0 to 7.3.0.10
-
Confirm the web interface is accessibleCheck if the Tivoli Application Dependency Discovery Manager web interface or API endpoints are reachable and processing HTTP requestsAffected if The web-facing component is active and handling requests
A user is affected if IBM Tivoli Application Dependency Discovery Manager version 7.3.0.0 through 7.3.0.10 is installed and the web interface is operational.
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.
dbcve · scoped7.3.0.11
Apply IBM's security patch (upgrade beyond 7.3.0.10) or implement a web application firewall to validate and sanitize HOST header values before processing.
7.3.0.11
- Check current IBM Tivoli Application Dependency Discovery Manager version to confirm it is between 7.3.0.0 and 7.3.0.10
- Obtain version 7.3.0.11 from IBM Fix Central or IBM Passport Advantage (search for TADDM or Tivoli Application Dependency Discovery Manager)
- Review IBM installation and upgrade documentation for the specific upgrade procedure
- Create a complete backup of the current TADDM installation including configuration files and database
- Stop all TADDM services before beginning the upgrade
- Apply version 7.3.0.11 using the IBM-provided upgrade process
- Restart TADDM services after upgrade completion
- Verify the installed version is now 7.3.0.11
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47143 — 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-2023-47143 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