Traffic decryption via fixed ServiceAgent cryptographic key
Published Feb 25, 2020 · Updated Aug 4, 2024
Use of hard-coded keys in Moxa AWK-3131A Series firmware 1.13 allows attackers to decrypt captured ServiceAgent network traffic. ServiceAgent marks packets whose byte 23 is between 0 and 5 as fixed-key traffic and applies an embedded key through AES-ECB. Attackers must capture traffic to or from TCP port 5801 or UDP port 5800; the demonstrated consequence is disclosure, not modification or interruption.
Summary
What happened
Use of hard-coded keys in Moxa AWK-3131A Series firmware 1.13 allows attackers to decrypt captured ServiceAgent network traffic. ServiceAgent marks packets whose byte 23 is between 0 and 5 as fixed-key traffic and applies an embedded key through AES-ECB. Attackers must capture traffic to or from TCP port 5801 or UDP port 5800; the demonstrated consequence is disclosure, not modification or interruption.
The record
- CVE
- CVE-2019-5137
- Published
- Feb 25, 2020
- Updated
- Aug 4, 2024
- Vendor
- Moxa
- Product
- AWK-3131A Series
- Classifications
- CWE-321, T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 25, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Moxa AWK-3131A Firmware version 1.13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo