Security readout for executives and security teams
Plain-English summary
YSoft SAFEQ 6 Server versions before 6.0.82 could expose stored LDAP credentials if an administrator changes LDAP settings from encrypted LDAPS to unencrypted LDAP pointing at a rogue server. This is not a drive-by internet attack in the provided sources; it depends on administrator-level configuration access.
Executive priority
Treat this as a controlled-access credential exposure risk, not an emergency internet-wide flaw based on provided evidence. Prioritize if SAFEQ integrates with sensitive directory credentials or admin governance is weak.
Technical view
The issue is an LDAP encryption downgrade path in SAFEQ 6 Server before 6.0.82. Changing the LDAP server URL from LDAPS to LDAP does not require password re-entry, so the existing credential may be sent in cleartext to a malicious LDAP endpoint. No CVSS, CWE, or affected CPE data is provided.
Likely exposure
Exposure is limited to organizations running YSoft SAFEQ 6 Server before 6.0.82 where administrators can modify LDAP configuration. Risk increases if admin accounts are shared, weakly controlled, or compromised.
Exploitation context
The CVE record does not report active exploitation, and CISA KEV status is false. The described scenario requires Admin access to change configuration, which the vendor cited when reconsidering the issue’s security classification.
Researcher notes
Evidence is sparse: no CVSS vector, CWE, CPEs, or exploit reporting are provided. The key technical condition is administrator-initiated LDAPS-to-LDAP downgrade without password re-entry, enabling cleartext credential exposure to a rogue LDAP server.
Mitigation direction
- Check whether SAFEQ 6 Server is older than 6.0.82.
- Review YSoft guidance for supported upgrade or remediation steps.
- Restrict SAFEQ administrative access to trusted personnel only.
- Require change control for LDAP configuration changes.
- Prefer LDAPS for directory connections where supported.
Validation and detection
- Inventory deployed SAFEQ 6 Server versions.
- Review LDAP server configuration for LDAPS versus LDAP usage.
- Check administrative audit logs for LDAP URL changes.
- Confirm admin accounts are individually assigned and access-controlled.
- Verify vendor guidance for version-specific remediation status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-35833 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://ysoft.com/CVE reference
- https://www.ysoft.com/en/legal/ldaps-encryption-downgrade-attack-vulnerabilityCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.