CVE-2022-23535 (High) detected in LiteDB-3.1.0.0.dll

[mend-bolt-for-github]

CVE-2022-23535 - High Severity Vulnerability

Vulnerable Library - LiteDB-3.1.0.0.dll

LiteDB

Library home page: https://api.nuget.org/packages/litedb.3.1.0.nupkg

Path to vulnerable library: /References/DNN/09.11.00/LiteDB.dll

Dependency Hierarchy:

• ❌ LiteDB-3.1.0.0.dll (Vulnerable Library)

Found in HEAD commit: 63b33f91192ce8e921ee01b7ebd0e913c7e9469a

Found in base branch: Develop

Vulnerability Details

LiteDB is a small, fast and lightweight .NET NoSQL embedded database. Versions prior to 5.0.13 are subject to Deserialization of Untrusted Data. LiteDB uses a special field in JSON documents to cast different types from BsonDocument to POCO classes. When instances of an object are not the same of class, BsonMapper use a special field _type string info with full class name with assembly to be loaded and fit into your model. If your end-user can send to your app a plain JSON string, deserialization can load an unsafe object to fit into your model. This issue is patched in version 5.0.13 with some basic fixes to avoid this, but is not 100% guaranteed when using Object type. The next major version will contain an allow-list to select what kind of Assembly can be loaded. Workarounds are detailed in the vendor advisory.

Publish Date: 2023-02-24

URL: CVE-2022-23535

CVSS 3 Score Details (7.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: Low
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.cve.org/CVERecord?id=CVE-2022-23535

Release Date: 2023-02-24

Fix Resolution: LiteDB - 5.0.13

---

Step up your Open Source Security Game with Mend here

[mend-bolt-for-github]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-bolt-for-github]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.