Token disclosure via PKCS1 v1.5 padding oracle
Published Jun 17, 2025 · Updated Jun 18, 2025
Padding-oracle exposure in conda-smithy before 3.47.1 allows remote attackers to recover encrypted Binstar tokens through Travis CI. travis_encrypt_binstar_token fetches a repository RSA public key and encrypts the token with PKCS1 v1.5 padding, whose distinguishable outcomes expose an oracle. Exploitation requires access to that oracle and modified ciphertext responses; the disclosed consequence is token plaintext recovery without the private key.
Summary
What happened
Padding-oracle exposure in conda-smithy before 3.47.1 allows remote attackers to recover encrypted Binstar tokens through Travis CI. travis_encrypt_binstar_token fetches a repository RSA public key and encrypts the token with PKCS1 v1.5 padding, whose distinguishable outcomes expose an oracle. Exploitation requires access to that oracle and modified ciphertext responses; the disclosed consequence is token plaintext recovery without the private key.
The record
- CVE
- CVE-2025-49824
- Published
- Jun 17, 2025
- Updated
- Jun 18, 2025
- Vendor
- conda-forge
- Product
- conda-smithy
- Classifications
- CWE-200
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2025CVE publishedPublication date reported by the CVE source.
- Jun 18, 2025Record 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=< 3.47.1
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
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