CVE-2025-8095
Weak OECH1 Prefix Encoding in OpenEdge Enables Data Exposure
Publication date: 2026-04-14
Last updated on: 2026-04-14
Assigner: Progress Software Corporation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| progress | openedge | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-257 | The storage of passwords in a recoverable format makes them subject to password reuse attacks by malicious users. In fact, it should be noted that recoverable encrypted passwords provide no significant benefit over plaintext passwords since they are subject not only to reuse by malicious attackers but also by malicious insiders. If a system administrator can recover a password directly, or use a brute force search on the available information, the administrator can use the password on other accounts. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability involves the OECH1 prefix encoding used in the OpenEdge platform. This encoding method is intended to obfuscate values but has been found to be cryptographically weak and unsuitable for stored encodings and enterprise applications. Because of its weaknesses, OECH1 encodings are considered exploitable and should be replaced immediately with other supported prefix encodings that use symmetric encryption.
How can this vulnerability impact me? :
This vulnerability can lead to the compromise of data security within the OpenEdge platform because the OECH1 encoding is weak and exploitable. Attackers could potentially decode or manipulate obfuscated values, leading to unauthorized access or data breaches. This impacts the confidentiality and integrity of sensitive information stored or processed using this encoding.
What immediate steps should I take to mitigate this vulnerability?
The OECH1 prefix encoding is cryptographically weak and should be considered exploitable.
Immediate mitigation involves replacing OECH1 encodings with any other supported prefix encoding that uses symmetric encryption.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability involves the OECH1 prefix encoding, which is cryptographically weak and unsuitable for enterprise applications. Since it is intended to obfuscate values but is exploitable, using it could lead to insufficient protection of sensitive data.
This weakness may impact compliance with standards and regulations such as GDPR and HIPAA, which require strong encryption and protection of personal and sensitive data. Failure to replace OECH1 encoding with stronger symmetric encryption methods could result in non-compliance due to inadequate data security controls.