Credential disclosure via Base64 data in URLs
Published Jan 13, 2021 · Updated Aug 3, 2024
Credential exposure in the 1C:Enterprise 8 Web server before 8.3.17.1851 allows remote attackers to obtain encoded credentials from URLs. The Web server places Base64-encoded credentials in the creds URL parameter, leaving secrecy dependent on URL handling rather than encryption. The affected Web server workflow must be exposed; the reported consequence is credential disclosure without integrity or availability impact.
Summary
What happened
Credential exposure in the 1C:Enterprise 8 Web server before 8.3.17.1851 allows remote attackers to obtain encoded credentials from URLs. The Web server places Base64-encoded credentials in the creds URL parameter, leaving secrecy dependent on URL handling rather than encryption. The affected Web server workflow must be exposed; the reported consequence is credential disclosure without integrity or availability impact.
The record
- CVE
- CVE-2021-3131
- Published
- Jan 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-326
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 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?
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