CVE-2021-45478: 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
CVE-2021-45478 is an access-control flaw in Yordam Library Automation System before 19.2. A logged-in user could collect data supplied by other users through improper parameter handling. The main business risk is unauthorized disclosure of library system data, not service outage or data tampering.
Executive priority
Treat as a moderate-priority confidentiality issue. It is not cited as actively exploited, but affected systems may expose user-provided data to authenticated users. Institutions running older versions should verify exposure and schedule remediation promptly.
Technical view
The CVE describes an IDOR-style parameter handling issue with CVSS 3.1 score 6.5: network exploitable, low privileges required, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact. Sources identify affected versions as before 19.2, but provide limited technical detail.
Likely exposure
Exposure is likely limited to organizations running Yordam Library Automation System versions before 19.2, especially if the application is reachable by regular authenticated users. The record does not prove exposure for other products or deployments.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The vulnerability requires some authenticated access, which lowers mass exploitation risk, but the network attack vector and high confidentiality impact make internal misuse and compromised-account scenarios relevant.
Researcher notes
Public details are sparse. The record maps the issue to CWE-233 and describes improper parameter handling allowing data collection as provided by users. There is a naming inconsistency between Yordam and Bordam in the source text, so preserve source wording when documenting scope.
Mitigation direction
Identify any Yordam Library Automation System deployments and their exact versions.
Prioritize upgrading systems before 19.2 after confirming vendor guidance.
Restrict application access to trusted users and networks where feasible.
Review role permissions for accounts with access to the system.
Monitor vendor and government advisories for remediation details.
Validation and detection
Confirm whether Library Automation System is present in the environment.
Check whether deployed versions are earlier than 19.2.
Review logs for unusual authenticated data access patterns.
Validate that low-privilege users cannot access other users' data.
Document findings and remediation status for affected instances.
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.