CVE-2024-1198
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 · uneditedA vulnerability, which was classified as critical, was found in openBI up to 6.0.3. Affected is the function addxinzhi of the file application/controllers/User.php of the component Phar Handler. The manipulation of the argument outimgurl leads to deserialization. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-252696.
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 confidenceA critical deserialization vulnerability in openBI (versions up to 6.0.3) exists in the addxinzhi function of application/controllers/User.php. The Phar Handler processes the outimgurl argument unsafely, allowing remote attackers to inject malicious phar:// payloads that trigger unsafe deserialization, likely leading to remote code execution.
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>= 6.0.0, <= 6.0.3CVSS 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 openBI versionLocate the version file or version identifier in your openBI installation (common locations include a version.php file, README, or admin panel). Compare this version against the affected range: 6.0.0 through 6.0.3.Affected if The installed version is 6.0.0, 6.0.1, 6.0.2, or 6.0.3.
-
Locate vulnerable scriptCheck if the file application/controllers/User.php exists in your openBI installation directory.Affected if The file application/controllers/User.php exists in the webroot.
-
Verify vulnerable function existsInspect application/controllers/User.php and search for the function named 'addxinzhi' (or addxinzhi).Affected if The addxinzhi function is present in User.php.
-
Check PHP phar configurationReview php.ini or run 'php -i' to check the phar.readonly setting. A value of 0 (disabled) allows phar deserialization.Affected if PHP has phar.readonly set to 0, enabling phar deserialization.
-
Confirm web exposureDetermine if the openBI application is accessible via HTTP/HTTPS (the vulnerable parameter 'outimgurl' must be reachable over the network for exploitation).Affected if The openBI application is accessible externally or internally via web and accepts user input.
Your environment is affected if openBI version is between 6.0.0 and 6.0.3 inclusive, the vulnerable User.php with addxinzhi function exists, and the outimgurl parameter is accessible forphar:// injection.
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 dataUpdate openBI to a patched version beyond 6.0.3. If no update is available, implement strict input validation on the outimgurl parameter to reject phar:// and other potentially malicious URL schemes, and disable phar deserialization entirely via phar.readonly=0 in php.ini.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1198 — 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-1198 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