CVE-2019-5137

HIGHNVD 7.57.5—

7.5

The usage of hard-coded cryptographic keys within the ServiceAgent binary allows for the decryption of captured traffic across the network from or to the Moxa AWK-3131A firmware version 1.13.

CVSS v3: 7.5
EG Score: 7.5(medium)
EPSS: 65.3%
KEV: Not listed

Published

February 25, 2020

Last Modified

November 21, 2024

References (2)

talos-cna@ciscohttps://talosintelligence.com/vulnerability_reports/TALOS-2019-0926
af854a3a-2127-422b-91ae-364da2661108https://talosintelligence.com/vulnerability_reports/TALOS-2019-0926

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 9× 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-05-27 13:39 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 07:17 UTCEG score recompute
2026-05-27 07:17 UTCGHSA enrichment
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

Frequently asked(5)

What is CVE-2019-5137?

CVE-2019-5137 is a high vulnerability published on February 25, 2020. The usage of hard-coded cryptographic keys within the ServiceAgent binary allows for the decryption of captured traffic across the network from or to the Moxa AWK-3131A firmware version 1.13.

When was CVE-2019-5137 disclosed?

CVE-2019-5137 was first published in the National Vulnerability Database on February 25, 2020, 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-5137 actively exploited?

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

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

CVE-2019-5137 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2019-5137?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-5137, 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-5137

Explore →

Is Your Infrastructure Affected by CVE-2019-5137?

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

Start Free Scan →Browse All CVEs

Frequently asked(5)

What is CVE-2019-5137?

When was CVE-2019-5137 disclosed?

Is CVE-2019-5137 actively exploited?

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

CVE-2019-5137 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2019-5137?

CVE-2019-5137

📅 Published

🔄 Last Modified

🔗 References (2)

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-5137?

CVE-2019-5137

📅 Published

🔄 Last Modified

🔗 References (2)

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-5137?

Published

Last Modified

References (2)

Frequently asked(5)

Published

Last Modified

References (2)

Frequently asked(5)