CVE-2019-6812

HIGHNVD 7.27.2—

7.2

A 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.

CVSS v3: 7.2
EG Score: 7.2(medium)
EPSS: 54.5%
KEV: Not listed

Published

May 22, 2019

Last Modified

November 21, 2024

References (4)

cybersecurity@sehttps://security.cse.iitk.ac.in/responsible-disclosure
cybersecurity@sehttps://www.schneider-electric.com/en/download/document/SEVD-2019-134-06/
af854a3a-2127-422b-91ae-364da2661108https://security.cse.iitk.ac.in/responsible-disclosure
af854a3a-2127-422b-91ae-364da2661108https://www.schneider-electric.com/en/download/document/SEVD-2019-134-06/

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-798Use of Hard-coded Credentials

Data Freshness Timeline

(refreshed 11× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-24 16:47 UTCepss_batch
2026-05-23 02:58 UTCEG score recompute
2026-05-23 02:58 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2019-6812?

CVE-2019-6812 is a high vulnerability published on May 22, 2019. A 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.

When was CVE-2019-6812 disclosed?

CVE-2019-6812 was first published in the National Vulnerability Database on May 22, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2019-6812 actively exploited?

CVE-2019-6812 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 54.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2019-6812?

CVE-2019-6812 has a CVSS v3 base score of 7.2 (NVD).

How do I remediate CVE-2019-6812?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-6812, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-6812

Explore →

Is Your Infrastructure Affected by CVE-2019-6812?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2019-6812

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-6812?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)