CVE-2019-13526
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 · uneditedDatalogic AV7000 Linear barcode scanner all versions prior to 4.6.0.0 is vulnerable to authentication bypass, which may allow an attacker to remotely execute arbitrary code.
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 confidenceThe Datalogic AV7000 Linear barcode scanner contains an authentication bypass vulnerability in versions prior to 4.6.0.0. An attacker can bypass authentication mechanisms to gain unauthorized access to the device's management interface, enabling remote code execution capabilities.
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< 4.6.0.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 the Datalogic AV7000 device on your networkScan your network for devices responding to typical Datalogic AV7000 protocols or check your network inventory for this specific device modelAffected if The device is present on your network and is a Datalogic AV7000 Linear barcode scanner
-
Determine the installed firmware versionAccess the device management interface (typically via web browser at the device IP address) and navigate to the firmware or system information page, or use the device's serial console to retrieve the firmware versionAffected if The firmware version displayed is less than 4.6.0.0 (for example, 4.5.x.x or earlier)
-
Verify management interface accessibilityAttempt to access the device web management interface over HTTP/HTTPS from an unauthorized network segment or test if authentication challenges are properly enforcedAffected if The management interface is accessible without proper authentication or authentication can be bypassed
-
Check for unauthorized access indicatorsReview device logs for failed authentication attempts, unexpected IP connections, or configuration changes made by unknown sourcesAffected if Logs show authentication bypass attempts or unauthorized access from unexpected IP addresses
You are affected if you have a Datalogic AV7000 scanner running firmware version prior to 4.6.0.0 and the management interface is accessible on your network.
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 data4.6.0.0
Upgrade Datalogic AV7000 firmware to version 4.6.0.0 or later. Until patched, isolate the device on a restricted network segment and monitor for unauthorized access attempts.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13526 — 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-2019-13526 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