CVE-2021-45477: IDOR in Yordam Library Automation System
Improper Handling of Parameters vulnerability in Bordam Information Technologies Library Automation System allows Collect Data as Provided by Users.
This issue affects Library Automation System: before 19.2.
Security readout for executives and security teams
Plain-English summary
A parameter-handling flaw in Yordam/Bordam Library Automation System before 19.2 may let a logged-in user retrieve data associated with other users. The main business risk is confidentiality: exposed library patron or operational data. Integrity and availability impact is not indicated in the source bundle.
Executive priority
Treat as a moderate-priority confidentiality issue. Prioritize if the system is internet-facing, holds sensitive patron data, or supports many low-privileged accounts.
Technical view
CVE-2021-45477 is described as improper handling of parameters, framed as an IDOR-style issue. CVSS 3.1 is 6.5: network-reachable, low complexity, requires low privileges, no user interaction, unchanged scope, high confidentiality impact, no integrity or availability impact.
Likely exposure
Exposure is most relevant to organizations running Yordam Library Automation System versions before 19.2, especially internet-accessible or broadly accessible library portals where authenticated users can access records.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. It indicates low-complexity network exploitation by a low-privileged authenticated user, but does not provide public exploit evidence.
Researcher notes
Evidence is limited to CVE metadata and cited Turkish government advisories. The USOM URL is marked broken in the bundle. No exploit details, proof of active exploitation, or detailed vendor fix notes are included.
Mitigation direction
Identify all Yordam Library Automation System deployments and their versions.
Upgrade systems before 19.2 to 19.2 or later where vendor guidance supports it.
Check the Turkish government advisory and vendor guidance for current remediation details.
Restrict portal access where feasible until version status is confirmed.
Review role and object-level authorization settings for sensitive records.
Validation and detection
Confirm deployed versions against the affected range: before 19.2.
Verify low-privileged users cannot access records outside their authorized scope.
Review logs for authenticated access patterns inconsistent with user role or ownership.
Check whether exposed portals are reachable from the internet.
Document remediation evidence and remaining exceptions for risk acceptance.
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-233: 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.
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-233 · source CWE mapping
Improper Handling of Parameters
Improper Handling of Parameters represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.