PII Leak Due to Change in EOR Handling
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Perforce | Delphix Continuous Compliance | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Microsoft | Ms-dos | — |
| Microsoft | Windows | — |
| Perforce | Perforce | — |
Vendor Solution
For all affected versions, verify that masked files use the correct EOR configuration and that the EOR setting matches the file format. * 1. Verify that EOR configuration matches the file format. * 2. Review masking job reports for expected row counts. * 3. Reconfigure jobs if discrepancies are found.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.279% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Perforce delphix Continuous Compliance
|
|
| CPEs | cpe:2.3:a:perforce:delphix_continuous_compliance:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Perforce delphix Continuous Compliance
|
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-200 | |
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Microsoft
Microsoft ms-dos Microsoft windows Perforce Perforce perforce |
|
| Vendors & Products |
Microsoft
Microsoft ms-dos Microsoft windows Perforce Perforce perforce |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In the versions of Delphix Continuous Compliance 2025.3.0 and above ,after a recent bug fix to correctly handle CR+LF (Windows and DOS) End-of-Record (EOR) characters in delimited files, an issue was identified: using an incorrect EOR configuration can cause inaccurate parsing and leave personally identifiable information (PII) unmasked. | In Delphix Continuous Compliance version 2025.3.0 and later, following a recent bug fix to correctly handle CR+LF (Windows and DOS) End-of-Record (EOR) characters in delimited files, an issue was identified: using an incorrect EOR configuration can cause inaccurate parsing and leave personally identifiable information (PII) unmasked. |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | After a recent bug fix to correctly handle CR+LF (Windows and DOS) End-of-Record (EOR) characters in delimited files, an issue was identified: using an incorrect EOR configuration can cause inaccurate parsing and leave personally identifiable information (PII) unmasked. | In the versions of Delphix Continuous Compliance 2025.3.0 and above ,after a recent bug fix to correctly handle CR+LF (Windows and DOS) End-of-Record (EOR) characters in delimited files, an issue was identified: using an incorrect EOR configuration can cause inaccurate parsing and leave personally identifiable information (PII) unmasked. |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | After a recent bug fix to correctly handle CR+LF (Windows and DOS) End-of-Record (EOR) characters in delimited files, an issue was identified: using an incorrect EOR configuration can cause inaccurate parsing and leave personally identifiable information (PII) unmasked. | |
| Title | PII Leak Due to Change in EOR Handling | |
| References |
| |
| Metrics |
cvssV4_0
|