Docker Mailbox
Monthly
CRLF injection in psyb0t/docker-mailbox before 0.4.13 allows a remote unauthenticated attacker to append arbitrary IMAP commands to the service's already-authenticated upstream mailbox connection when bearer-token authentication is not configured. Attacker-controlled folder, UID, or search values are passed into IMAP command construction without neutralization, yielding high integrity and availability impact on the mail store; the exposed path only exists on instances deployed without bearer-token auth, and no public exploit has been identified at time of analysis. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects a network-reachable, low-complexity, no-interaction flaw, though real-world risk is constrained by the non-default configuration requirement and the project's very small deployment base.
CRLF injection in psyb0t/docker-mailbox before 0.4.13 allows a remote unauthenticated attacker to append arbitrary IMAP commands to the service's already-authenticated upstream mailbox connection when bearer-token authentication is not configured. Attacker-controlled folder, UID, or search values are passed into IMAP command construction without neutralization, yielding high integrity and availability impact on the mail store; the exposed path only exists on instances deployed without bearer-token auth, and no public exploit has been identified at time of analysis. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects a network-reachable, low-complexity, no-interaction flaw, though real-world risk is constrained by the non-default configuration requirement and the project's very small deployment base.