Unspecified impact via zmq3 format strings
Published Aug 6, 2017 · Updated Dec 27, 2024
Format string injection in rsyslog before 8.28.0 allows attackers to cause unspecified impact via zmq3 description fields. imzmq3 createSocket and omzmq3 initZMQ pass each description directly as the zsocket_bind or zsocket_connect format argument rather than through a fixed %s format. Public sources do not establish how attackers can influence these configuration-derived descriptions or what concrete consequence follows.
Summary
What happened
Format string injection in rsyslog before 8.28.0 allows attackers to cause unspecified impact via zmq3 description fields. imzmq3 createSocket and omzmq3 initZMQ pass each description directly as the zsocket_bind or zsocket_connect format argument rather than through a fixed %s format. Public sources do not establish how attackers can influence these configuration-derived descriptions or what concrete consequence follows.
The record
- CVE
- CVE-2017-12588
- Published
- Aug 6, 2017
- Updated
- Dec 27, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-134
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 6, 2017CVE publishedPublication date reported by the CVE source.
- Dec 27, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
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