CVE-2024-34336: User enumeration vulnerability in ORDAT FOSS-Online before v2.24.01 allows attackers to determine if an acc...
User enumeration vulnerability in ORDAT FOSS-Online before v2.24.01 allows attackers to determine if an account exists in the application by comparing the server responses of the forgot password functionality.
Security readout for executives and security teams
Plain-English summary
CVE-2024-34336 lets an unauthenticated attacker tell whether a user account exists in ORDAT FOSS-Online by observing differences in forgot-password responses. This does not directly expose passwords or data, but it can support targeted phishing, credential attacks, and privacy leakage.
Executive priority
Treat as a moderate-priority privacy and account-security issue. It is not a direct system compromise, but it can make targeted attacks easier and should be addressed in the normal vulnerability remediation cycle.
Technical view
The issue is a CWE-204 observable-response discrepancy in the forgot password workflow of ORDAT FOSS-Online before v2.24.01. CVSS 3.1 is 5.3: network-accessible, low complexity, no privileges or user interaction required, with low confidentiality impact only.
Likely exposure
Organizations running ORDAT FOSS-Online versions before v2.24.01 are the likely exposure group. The bundle does not provide CPEs or detailed affected-version metadata beyond that version boundary.
Exploitation context
The source bundle does not indicate active exploitation, and CISA KEV status is false. Exploitation would mainly provide account-existence information, which can improve the targeting of later social engineering or authentication attacks.
Researcher notes
Evidence is limited to the CVE record and the referenced disclosure. The structured affected data is not populated with vendor, product, CPE, or detailed version ranges, so validation should rely on local product inventory and vendor documentation.
Mitigation direction
Review ORDAT guidance for CVE-2024-34336 and update affected systems to v2.24.01 or later.
Ensure forgot-password responses are uniform for existing and nonexistent accounts.
Monitor authentication and password-reset telemetry for abnormal enumeration patterns.
Apply rate limiting and abuse controls around account-recovery workflows.
Validation and detection
Inventory ORDAT FOSS-Online deployments and confirm their running versions.
Check whether any instance remains below v2.24.01.
In authorized testing, confirm account-recovery responses do not reveal account existence.
Review logs for repeated password-reset probes across many identifiers.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cwe · low confidence lookup
CWE-204: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-204 · source CWE mapping
Observable Response Discrepancy
Observable Response Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.