CVE-2019-6812
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 · uneditedA CWE-798 use of hardcoded credentials vulnerability exists in BMX-NOR-0200H with firmware versions prior to V1.7 IR 19 which could cause a confidentiality issue when using FTP protocol.
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 confidenceA CWE-798 hardcoded credentials vulnerability exists in the BMX-NOR-0200H industrial network device firmware versions prior to V1.7 IR 19. The embedded credentials used for FTP protocol authentication can be discovered and exploited, allowing unauthorized access to the device and potential confidentiality breach of data transmitted via FTP.
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= 1.7CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Confirm device model is BMX-NOR-0200HAccess the device web interface, console, or management software and verify the exact model number displayed in device information or system statusAffected if Device model is not BMX-NOR-0200H (different models are not affected by this specific CVE)
-
Check firmware versionLocate the firmware version in the device web interface under System Information, or via console command such as 'show version' or 'sys info', or through the management software firmware propertiesAffected if Firmware version is prior to V1.7 IR 19 (versions 1.0 through 1.6.x are affected; version 1.7 IR 19 and later are not)
-
Verify if FTP service is enabledCheck device network services or protocol settings in the web interface or console - look for FTP server status, or scan the device IP for open port 21Affected if FTP service is enabled and port 21 is open (the hardcoded credentials can only be exploited if FTP is active)
-
Assess network exposure of FTP portFrom an external or internal scanning position, verify if port 21 is reachable on the device IP address, or review firewall/network ACL rules allowing FTP accessAffected if Port 21 is reachable from untrusted networks (the vulnerability is exploitable when FTP is network-accessible)
The environment is affected if the device is a BMX-NOR-0200H running firmware version prior to V1.7 IR 19 with FTP service enabled and accessible on the 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 dataUpgrade BMX-NOR-0200H firmware to version V1.7 IR 19 or later to remove the hardcoded credentials. If immediate patching is not possible, restrict network access to FTP ports and monitor for unauthorized access attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6812 — 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-6812 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