Felix Health Check Webconsole PluginPlugin / extension · Apache
CVE-2023-38435
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 · uneditedAn improper neutralization of input during web page generation ('Cross-site Scripting') [CWE-79] vulnerability in Apache Felix Healthcheck Webconsole Plugin version 2.0.2 and prior may allow an attacker to perform a reflected cross-site scripting (XSS) attack. Upgrade to Apache Felix Healthcheck Webconsole Plugin 2.1.0 or higher.
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 confidenceA reflected cross-site scripting (XSS) vulnerability in Apache Felix Healthcheck Webconsole Plugin versions 2.0.2 and prior allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in web console responses.
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
Felix Health Check Webconsole PluginPlugin / extension
< 2.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Apache Felix Healthcheck Webconsole Plugin is installedCheck for the healthcheck webconsole bundle in the OSGi runtime. In the Apache Felix OSGi console, run 'lb' or 'list' and look for a bundle containing 'healthcheck' and 'webconsole' in its name. Alternatively, inspect the 'bundles' directory for a JAR file named similarly to 'org.apache.felix.healthcheck.webconsole-X.X.X.jar'.Affected if The plugin bundle is not found in the OSGi runtime
-
Determine the installed version of the pluginIf the bundle is found, run 'inspect cap service' in the OSGi console for the healthcheck bundle, or examine the JAR file's MANIFEST.MF for the 'Bundle-Version' attribute. The JAR filename often contains the version number (e.g., org.apache.felix.healthcheck.webconsole-2.0.2.jar).Affected if The version is 2.0.2 or lower, or if the version cannot be determined and is therefore assumed to be vulnerable
-
Check if the Apache Felix Web Console is enabled and accessibleAttempt to access the Felix Web Console via HTTP on the typical port (usually port 8080 or as configured). The URL pattern is typically /system/console. If the console responds and presents a login or status page, it is enabled.Affected if The web console is accessible and the healthcheck plugin is installed; the XSS only triggers through console requests
-
Verify the webconsole plugin is registered in the consoleIn the Felix Web Console, navigate to the 'Healthcheck' section (typically under a 'Health Check' menu item). If the page loads and displays healthcheck functionality, the plugin is active in the web console.Affected if The Healthcheck plugin page loads in the web console and accepts user input in any form fields
You are affected if the Apache Felix Healthcheck Webconsole Plugin is installed, the web console is accessible, and the installed version is below 2.1.0.
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 · scoped2.1.0
Upgrade Apache Felix Healthcheck Webconsole Plugin to version 2.1.0 or higher to remediate this reflected XSS vulnerability.
2.1.0
- Download Apache Felix Healthcheck Webconsole Plugin version 2.1.0 or higher from the official Apache Felix distribution repository
- Stop the Apache Felix framework or the specific bundle if currently running
- Replace the existing healthcheck-webconsole-plugin JAR file with the new version 2.1.0 or higher
- Restart the Apache Felix framework or the updated bundle to load the new plugin
- Verify the plugin loads correctly and the webconsole is accessible
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Felix Health Check Webconsole Plugin
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38435 — 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-38435 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