dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-4019

MEDIUM · 6.3 CVSS v3.1 Published 2024-04-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
A vulnerability classified as critical has been found in Byzoro Smart S80 Management Platform up to 20240411. Affected is an unknown function of the file /importhtml.php. The manipulation of the argument sql leads to deserialization. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-261666 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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 PHP deserialization vulnerability exists in Byzoro Smart S80 Management Platform (versions up to 20240411) in the /importhtml.php file. The 'sql' argument is passed to an unsafe unserialize() call, allowing remote attackers to inject malicious serialized PHP objects. The exploit is publicly available, increasing exploitation likelihood.

MitigationReplace unsafe deserialization of the 'sql' parameter with parameterized queries or safe parsing logic; if the parameter is unnecessary, remove the vulnerable function entirely. Consider deploying a WAF rule to block deserialization attempts while remediation is underway.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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. Confirm Byzoro Smart S80 Management Platform installation
    Identify if the target system is running Byzoro Smart S80 Management Platform. Check the web interface banner, HTTP headers, or consult system documentation for the product name and version.
    Affected if The system is confirmed to be Byzoro Smart S80 Management Platform.
  2. Check the product version against affected range
    Determine the installed version of Byzoro Smart S80 Management Platform. Compare it to the affected version range (versions up to and including 20240411).
    Affected if The installed version is 20240411 or earlier.
  3. Verify the vulnerable file exists
    Check if the file /importhtml.php exists on the web server. This can be done by attempting to access the URL directly (e.g., GET request to http://[target]/importhtml.php).
    Affected if The file /importhtml.php is present and accessible on the server.
  4. Inspect the unserialize() call behavior
    Analyze the /importhtml.php file source code to confirm that the 'sql' parameter is passed to the unserialize() function without proper sanitization.
    Affected if The 'sql' parameter is processed through an unsafe unserialize() call in the code.
  5. Test for deserialization injection
    If direct code inspection is not possible, observe whether the application accepts serialized PHP data through the 'sql' parameter and processes it. This may manifest as unexpected behavior or errors when malformed serialized data is submitted.
    Affected if The application accepts and processes the 'sql' parameter through unserialize() without validation.

A system is affected if it runs Byzoro Smart S80 Management Platform version 20240411 or earlier and the /importhtml.php file exists with the unsafe unserialize() call handling the 'sql' 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace unsafe deserialization of the 'sql' parameter with parameterized queries or safe parsing logic; if the parameter is unnecessary, remove the vulnerable function entirely. Consider deploying a WAF rule to block deserialization attempts while remediation is underway.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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