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.
History

Mon, 22 Dec 2025 17:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Sun, 21 Dec 2025 21:30:00 +0000

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

Sat, 20 Dec 2025 15:45:00 +0000

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.

Sat, 20 Dec 2025 13:00:00 +0000

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.

Sat, 20 Dec 2025 03:30:00 +0000

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

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: Perforce

Published: 2025-12-20T03:04:21.183Z

Updated: 2025-12-22T16:11:52.890Z

Reserved: 2025-12-12T16:01:02.586Z

Link: CVE-2025-14591

cve-icon Vulnrichment

Updated: 2025-12-22T16:11:47.818Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2025-12-20T04:16:08.017

Modified: 2025-12-23T14:51:52.650

Link: CVE-2025-14591

cve-icon Redhat

No data.