Information disclosure via static CBC initialization vector
Published Nov 16, 2023 · Updated Jul 9, 2026
Insecure CBC encryption in PyPinkSign 0.5.1 and earlier allows remote attackers to infer plaintext patterns from encrypted messages. The seed_cbc_128_encrypt functions default to the same 16-byte initialization vector for every encryption operation instead of generating a fresh unpredictable value. Exploitation requires access to ciphertexts produced under the repeated default vector and exposes message patterns rather than encryption keys or write access.
Summary
What happened
Insecure CBC encryption in PyPinkSign 0.5.1 and earlier allows remote attackers to infer plaintext patterns from encrypted messages. The seed_cbc_128_encrypt functions default to the same 16-byte initialization vector for every encryption operation instead of generating a fresh unpredictable value. Exploitation requires access to ciphertexts produced under the repeated default vector and exposes message patterns rather than encryption keys or write access.
The record
- CVE
- CVE-2023-48056
- Published
- Nov 16, 2023
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-330
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 16, 2023CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record 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.
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
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