Memory read and write via format-string prefix
Published Apr 5, 2021 · Updated Aug 3, 2024
Format string injection in libpano13 2.9.20_rc2 and earlier allows attackers to read or write process memory via a filename prefix. panoFileOutputNamesCreate() accepts percentage signs in an externally controlled filename-prefix string, causing formatting directives to be interpreted instead of treated as filename text. An application must pass an attacker-controlled prefix into the affected function; exploitation exposes or modifies that application's process memory, while malformed prefixes can crash it.
Summary
What happened
Format string injection in libpano13 2.9.20_rc2 and earlier allows attackers to read or write process memory via a filename prefix. panoFileOutputNamesCreate() accepts percentage signs in an externally controlled filename-prefix string, causing formatting directives to be interpreted instead of treated as filename text. An application must pass an attacker-controlled prefix into the affected function; exploitation exposes or modifies that application's process memory, while malformed prefixes can crash it.
The record
- CVE
- CVE-2021-20307
- Published
- Apr 5, 2021
- Updated
- Aug 3, 2024
- Vendor
- Panorama Tools
- Product
- libpano13
- Classifications
- CWE-134, CAPEC-135
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 5, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=libpano13 2.9.20_rc3
What conditions does exploitation require?
What is affected?
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