Authenticated code execution via unbounded username formatting
Published Feb 25, 2020 · Updated Aug 4, 2024
Stack-based buffer overflow in Moxa AWK-3131A firmware 1.13 allows remote authenticated users to execute code via an imported configuration. During user-account validation, iw_configbyINI passes an oversized username to sprintf, which writes the error message into a fixed stack buffer without bounds checking. A low-privilege account that can import a crafted configuration can overwrite the saved return address and control execution flow.
Summary
What happened
Stack-based buffer overflow in Moxa AWK-3131A firmware 1.13 allows remote authenticated users to execute code via an imported configuration. During user-account validation, iw_configbyINI passes an oversized username to sprintf, which writes the error message into a fixed stack buffer without bounds checking. A low-privilege account that can import a crafted configuration can overwrite the saved return address and control execution flow.
The record
- CVE
- CVE-2019-5153
- Published
- Feb 25, 2020
- Updated
- Aug 4, 2024
- Vendor
- Moxa
- Product
- AWK-3131A Series
- Classifications
- CWE-787, CWE-121, T1190
- Attack vector
- network
- Privileges
- authenticated
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.
Weakness, pattern, technique
Public exploit references
- Talos configuration-import control-flow demonstrationproof of concept · demonstrated
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