dbcve.org
OpenbiApplication

CVE-2024-1114

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-31
Fix available
A fix is available. Upgrade to after 1.0.8 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
A vulnerability has been found in openBI up to 1.0.8 and classified as critical. This vulnerability affects the function dlfile of the file /application/index/controller/Screen.php. The manipulation of the argument fileUrl leads to improper access controls. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-252472.

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

A critical improper access control vulnerability exists in openBI up to v1.0.8 in the dlfile function within /application/index/controller/Screen.php. The fileUrl parameter is not properly validated or authorized, allowing remote unauthenticated attackers to download arbitrary files from the server, potentially exposing sensitive system files, credentials, or configuration data.

MitigationImplement strict access control checks and input validation on the fileUrl parameter in the dlfile function to ensure users can only access files they are authorized to download. Restrict file paths to an allowed whitelist and validate that the requested path resolves within an approved directory.

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
OpenbiApplication
Affected:<= 1.0.8

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 openBI installation
    Locate the web application directory. Common paths include /var/www/, /opt/, or the web root. Look for directories named 'openbi', 'Openbi', or the presence of an 'application' folder containing 'index/controller/Screen.php'.
    Affected if The application directory with the structure application/index/controller/Screen.php exists on the server.
  2. Determine openBI version
    Check for a version file in the openBI installation directory, or inspect the source code for a version constant. Common locations include a version.php file in the root or config directory, or search for a VERSION or VERSION_NO constant in the PHP files.
    Affected if The installed version is 1.0.8 or lower.
  3. Verify vulnerable Screen.php exists
    Confirm the file /application/index/controller/Screen.php exists in the openBI installation. This file contains the dlfile function that handles file downloads.
    Affected if The Screen.php file exists in the expected path within the application directory.
  4. Check dlfile function accessibility
    Attempt to access the dlfile function via the web interface without authentication. The endpoint typically follows the pattern: http://[host]/index.php/screen/dlfile?fileUrl=../../../../../../etc/passwd or similar path traversal. Check if the application allows unauthenticated access to this endpoint.
    Affected if The dlfile function is reachable without authentication and accepts a fileUrl parameter without proper validation.
  5. Test for arbitrary file download
    Send a crafted request to the dlfile endpoint with a fileUrl parameter pointing to a sensitive file such as ../../../../etc/passwd, ../../../../win.ini, or the application's configuration file containing database credentials. Inspect the response to see if the file contents are returned.
    Affected if The server returns the contents of files outside the intended web directory without authentication.

If openBI version 1.0.8 or lower is installed and the dlfile function in Screen.php is accessible without authentication, the system is vulnerable to arbitrary file disclosure via path traversal in the fileUrl parameter.

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.

From vendor data
Upgrade available Upgrade to a release after 1.0.8
Interim mitigation

Implement strict access control checks and input validation on the fileUrl parameter in the dlfile function to ensure users can only access files they are authorized to download. Restrict file paths to an allowed whitelist and validate that the requested path resolves within an approved directory.

Fix this in Openbi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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