dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-3346

MEDIUM · 6.3 CVSS v3.1 Published 2024-04-05
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 was found in Byzoro Smart S80 up to 20240328. It has been declared as critical. This vulnerability affects unknown code of the file /log/webmailattach.php. The manipulation of the argument mail_file_path leads to os command injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-259450 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

OS command injection vulnerability in Byzoro Smart S80 network management device. The /log/webmailattach.php script does not properly sanitize the mail_file_path parameter before passing it to a system call, allowing remote attackers to execute arbitrary OS commands.

MitigationSince the vendor is unresponsive, implement compensating controls: restrict network access to the device management interface via firewall, deploy WAF rules to block suspicious patterns in the mail_file_path parameter, or disable the webmail functionality if not required.

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 device is Byzoro Smart S80
    Identify the network management device model via web interface banner, SNMP sysDescr, or hardware labeling. Check device management web interface at port 80/443 for Byzoro branding.
    Affected if The device is a Byzoro Smart S80 network management appliance.
  2. Locate vulnerable webmail script
    Attempt to access /log/webmailattach.php on the device web server. Use curl or browser to request: http://[device-ip]/log/webmailattach.php
    Affected if The script exists and responds (even with an error), indicating the vulnerable code is present.
  3. Verify webmail functionality is enabled
    Check if webmail features are accessible. Attempt to access the webmail login page or check device configuration for webmail service status.
    Affected if Webmail functionality is enabled and the /log/webmailattach.php endpoint is reachable without authentication or with low-privilege auth.
  4. Inspect mail_file_path parameter handling
    Review web server access logs or application logs for requests to webmailattach.php containing the mail_file_path parameter. Use grep: grep -i 'webmailattach.php' /var/log/[access or application logs]
    Affected if Requests to webmailattach.php with mail_file_path parameter are present, confirming the attack surface is exposed.
  5. Compare firmware version against vendor releases
    Check device firmware version in web interface (typically under System > Device Info or similar) or via SNMP. Compare against any available Byzoro firmware release notes.
    Affected if Firmware version cannot be confirmed as patched because vendor has not released an update for this vulnerability.

If the device is a Byzoro Smart S80 with the /log/webmailattach.php script accessible and webmail enabled, the environment is vulnerable to command injection via the mail_file_path 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

Since the vendor is unresponsive, implement compensating controls: restrict network access to the device management interface via firewall, deploy WAF rules to block suspicious patterns in the mail_file_path parameter, or disable the webmail functionality if not required.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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