Silent client-side encryption bypass via unescaped field-name regex in CSFLE schema builder
Résumé
A client-side encryption schema construction component in the MongoDB C# Driver places caller-supplied field identifiers into a position that is interpreted as a pattern expression, without normalizing or validating them. As a result, an application that designates certain fields for client-side fie...
Résumé IA
Rédigé par une IA externe ; il peut contenir des erreurs. Vérifiez la description d'origine et les références ci-dessous avant d'agir.
MongoDB C# Driverの CSFLE スキーマ構築部分で、指定されたフィールド名が正規表現として解釈される問題があります。暗号化の指定が適用されず、データが平文で保存・返却されるおそれがあり、暗号化キーを持たない第三者でも閲覧できる場合があります。3.5.0 以降 3.13.0 未満が影響を受け、3.13.0 で修正されています。3.13.0 以降へ更新してください。
Paquets affectés
| Écosystème | Paquet | Concernées | Corrigé |
|---|---|---|---|
| MongoDB | C# Driver |
≥ 3.5.0, < 3.13.0 |
3.13.0 |
Description d'origine La description telle que publiée par la source (souvent en anglais).
A client-side encryption schema construction component in the MongoDB C# Driver places caller-supplied field identifiers into a position that is interpreted as a pattern expression, without normalizing or validating them. As a result, an application that designates certain fields for client-side field-level encryption may have the protection silently fail to apply, so data intended to be encrypted is stored and returned in cleartext; conversely, the rule may apply more broadly than intended. No user action is required to cause the condition, and any party with ordinary read access to the stored data — without possession of the encryption keys — can observe the unprotected values.
Source: CVE.org (CVE Program・cvelistV5) NVD
Références
- web cna@mongodb.com
- web cna@mongodb.com
- web cna@mongodb.com