dbcve.org
Business Intelligence And Reporting ToolsApplication · Eclipse

CVE-2023-0100

HIGH · 8.8 CVSS v3.1 Published 2023-03-15
Fix available
A fix is available. Upgrade to 4.13.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
In Eclipse BIRT, starting from version 2.6.2, the default configuration allowed to retrieve a report from the same host using an absolute HTTP path for the report parameter (e.g. __report=http://xyz.com/report.rptdesign). If the host indicated in the __report parameter matched the HTTP Host header value, the report would be retrieved. However, the Host header can be tampered with on some configurations where no virtual hosts are put in place (e.g. in the default configuration of Apache Tomcat) or when the default host points to the BIRT server. This vulnerability was patched on Eclipse BIRT 4.13.

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

Eclipse BIRT versions 2.6.2 through pre-4.13 contain a Server-Side Request Forgery (SSRF) vulnerability where the __report parameter accepts absolute HTTP paths and performs insufficient validation of the Host header. Attackers can manipulate the Host header in configurations without virtual hosts (e.g., default Apache Tomcat) to retrieve reports from the local server or conduct internal network reconnaissance.

MitigationUpgrade Eclipse BIRT to version 4.13 or later which contains the patch for proper host header validation. If immediate upgrade is not feasible, implement network-level controls to restrict Host header manipulation.

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
Business Intelligence And Reporting ToolsApplication
Affected:>= 2.6.2, < 4.13.0

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Eclipse BIRT version
    Locate the BIRT installation and check version information in manifest files (MANIFEST.MF), about dialog, or version.properties. Common locations include the WebViewerExample or birt.war deployment directory.
    Affected if The installed version is 2.6.2 or higher but lower than 4.13.0
  2. Confirm server configuration lacks virtual hosts
    Examine the server configuration (e.g., server.xml for Apache Tomcat) to determine if virtual host mapping is in use. Default Tomcat installations typically have no <Host> entries beyond the default localhost.
    Affected if The application is deployed on a server without explicit virtual host configuration (default Apache Tomcat setup)
  3. Verify __report parameter endpoint accessibility
    Test if the BIRT report viewer is accessible via HTTP. The vulnerability exists when the report parameter (typically __report) accepts absolute paths. Try accessing a known BIRT endpoint such as /birt/frameset?__report=example.rptdesign
    Affected if The BIRT viewer is accessible and accepts the __report parameter without additional authentication or validation
  4. Check Host header validation
    Send a request to the BIRT endpoint with a manipulated Host header (e.g., Host: internal-network-ip) and observe if the application processes requests to arbitrary hosts.
    Affected if The application accepts and processes Host headers from external sources without proper validation, allowing SSRF

You are affected if Eclipse BIRT version 2.6.2 through 4.12.x is deployed on a server without virtual hosts and the __report parameter endpoint is accessible without proper Host header validation.

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

Upgrade Eclipse BIRT to version 4.13 or later which contains the patch for proper host header validation. If immediate upgrade is not feasible, implement network-level controls to restrict Host header manipulation.

Recommended fix High confidence

4.13.0 or later

  1. 1. Identify the current Eclipse BIRT version in use by checking the installed libraries or application metadata
  2. 2. Backup the current Eclipse BIRT deployment and any custom reports
  3. 3. Download Eclipse BIRT version 4.13.0 or later from the official Eclipse repository (eclipse.org/projects/birt)
  4. 4. Replace the existing BIRT runtime libraries with the new version 4.13.0 or newer
  5. 5. Restart the application server hosting BIRT
  6. 6. Verify the __report parameter is no longer vulnerable to arbitrary URL injection
  7. 7. Test that existing reports still render correctly with the new version
Caveat Review release notes between current version and 4.13.0 for any API or behavior changes that may affect custom report templates

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

Fix this in Business Intelligence And Reporting Tools Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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