dbcve.org
A320 FirmwareOperating system · Marel

CVE-2017-6041

CRITICAL · 9.8 CVSS v3.0 Published 2017-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An Unrestricted Upload issue was discovered in Marel Food Processing Systems M3000 terminal associated with the following systems: A320, A325, A371, A520 Master, A520 Slave, A530, A542, A571, Check Bin Grader, FlowlineQC T376, IPM3 Dual Cam v132, IPM3 Dual Cam v139, IPM3 Single Cam v132, P520, P574, SensorX13 QC flow line, SensorX23 QC Master, SensorX23 QC Slave, Speed Batcher, T374, T377, V36, V36B, and V36C; M3210 terminal associated with the same systems as the M3000 terminal identified above; M3000 desktop software associated with the same systems as the M3000 terminal identified above; MAC4 controller associated with the same systems as the M3000 terminal identified above; SensorX23 X-ray machine; SensorX25 X-ray machine; and MWS2 weighing system. This vulnerability allows an attacker to modify the operation and upload firmware changes without detection.

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

An unrestricted upload vulnerability in Marel Food Processing Systems (M3000, M3210 terminals, MAC4 controller, SensorX23/X25 X-ray machines, and MWS2 weighing system) allows unauthenticated attackers to upload arbitrary firmware modifications without detection, potentially enabling complete system compromise.

MitigationImplement authenticated firmware uploads with cryptographic code signing verification and deploy integrity monitoring to detect unauthorized firmware changes.

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
A320 FirmwareOperating system
Affected:all versions
A325 FirmwareOperating system
Affected:all versions
A371 FirmwareOperating system
Affected:all versions
A520 Master FirmwareOperating system
Affected:all versions
A520 Slave FirmwareOperating system
Affected:all versions
A530 FirmwareOperating system
Affected:all versions
A542 FirmwareOperating system
Affected:all versions
A571 FirmwareOperating system
Affected:all versions

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.0/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 Marel food processing systems in your environment
    Inventory your network for Marel M3000 or M3210 terminals, MAC4 controllers, SensorX23 or SensorX25 X-ray machines, or MWS2 weighing systems
    Affected if Any of these Marel products are present in the environment
  2. Determine the installed firmware version
    Access the device management interface and navigate to the firmware information or system status section to identify the firmware version number
    Affected if The firmware version matches A320, A325, A371, A520 (Master or Slave), A530, A542, or A571 regardless of version number - all versions are affected
  3. Check if the device web interface is network accessible
    Verify whether the Marel device management web interface is exposed to the network or internet by reviewing firewall rules and network segmentation
    Affected if The device management interface is reachable from untrusted network segments or the internet
  4. Inspect firmware upload mechanism for authentication
    Access the firmware update section of the device web interface and attempt to determine if authentication is required or if the upload endpoint accepts requests without credentials
    Affected if Firmware upload does not require valid authentication credentials or accepts unauthenticated requests

You are affected if you have any Marel M3000, M3210, MAC4, SensorX23/X25, or MWS2 devices running the listed firmware versions with an accessible management interface that allows unauthenticated firmware uploads.

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

Implement authenticated firmware uploads with cryptographic code signing verification and deploy integrity monitoring to detect unauthorized firmware changes.

Fix this in A320 Firmware Scoped from the published advisory
  • Consultation16.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA12.0 h
92.0 hours of engineering $16,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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