dbcve.org
Linear Emerge 50p FirmwareOperating system · Nortekcontrol

CVE-2019-7271

CRITICAL · 9.8 CVSS v3.0 Published 2019-07-01
Fix available
A fix is available. Upgrade to after 4.6.07 or later.
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
Nortek Linear eMerge 50P/5000P devices have Default Credentials.

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

The Nortek Linear eMerge 50P and 5000P physical access control devices ship with hardcoded default credentials that allow unauthenticated attackers to gain full administrative access to the device management interface. This is a critical flaw as it requires no special knowledge or interaction to exploit.

MitigationImmediately change all default credentials on affected devices to strong, unique passwords, disable remote administrative access if not required, and implement network segmentation to limit exposure of management interfaces.

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
Linear Emerge 50p FirmwareOperating system
Affected:<= 4.6.07
Linear Emerge 5000p FirmwareOperating system
Affected:<= 4.6.07

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 the device model
    Access the device web interface or use network scanning (e.g., nmap, banner grabbing) to confirm the device is a Nortekcontrol Linear eMerge 50P or 5000P. The device typically exposes an HTTP management interface on common ports (80, 443, or 8080).
    Affected if The device model is confirmed to be a Linear eMerge 50P or 5000P physical access control panel.
  2. Determine the installed firmware version
    Log into the device web interface and navigate to the System Information, About, or Status page to view the firmware version. Alternatively, check via SNMP or the device API if accessible. Compare the version number against the affected range.
    Affected if The firmware version is 4.6.07 or lower.
  3. Verify default credential status
    Attempt to access the device management interface using the known hardcoded default credentials for this device platform. If login succeeds with default credentials, the vulnerability is present. Alternatively, check if credentials have been changed from factory defaults.
    Affected if Default administrative credentials are still active or have not been changed from the manufacturer defaults.
  4. Assess network exposure of management interface
    Determine if the device management interface is accessible from untrusted networks (such as the internet or guest networks) by reviewing firewall rules, VLAN configuration, or by performing a port scan from an external location.
    Affected if The administrative interface is exposed to untrusted networks without firewall protection.

A user is affected if the device is a Linear eMerge 50P or 5000P with firmware version 4.6.07 or lower, and the default hardcoded credentials remain active or the management interface is accessible from untrusted networks.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 4.6.07
Interim mitigation

Immediately change all default credentials on affected devices to strong, unique passwords, disable remote administrative access if not required, and implement network segmentation to limit exposure of management interfaces.

Recommended fix Moderate confidence
  1. Access the Linear eMerge 50P/5000P web administration interface using the device's IP address
  2. Log in using the default administrative credentials (refer to vendor documentation for the specific default username/password combination)
  3. Navigate to the user management or authentication settings section
  4. Change the default administrative password to a strong, unique password following best practices (minimum 12 characters, mixed case, numbers, and special characters)
  5. If available, create additional user accounts with appropriate privilege levels and disable or remove any unused default accounts
  6. Save the configuration changes and restart the device if required
  7. Verify the new credentials work by logging out and logging back in
  8. Document the new credentials in a secure password manager

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linear Emerge 50p Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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