Custom CTCP will leak the real reply #388

Closed
opened 2026-10-05 04:17:41 +02:00 by adam · 1 comment
Owner

If you set a custom ctcp reply and save then spam the user with ctcp it will eventually leak the real reply.

Example of the problem (spamming /ctcp version):

12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION - Custom CTCP Reply -
12:00 AM <username> VERSION * Client CTCP Reply *
If you set a custom ctcp reply and save then spam the user with ctcp it will eventually leak the real reply. Example of the problem (spamming /ctcp <username> version): ``` 12:00 AM <username> VERSION - Custom CTCP Reply - 12:00 AM <username> VERSION - Custom CTCP Reply - 12:00 AM <username> VERSION - Custom CTCP Reply - 12:00 AM <username> VERSION - Custom CTCP Reply - 12:00 AM <username> VERSION - Custom CTCP Reply - 12:00 AM <username> VERSION - Custom CTCP Reply - 12:00 AM <username> VERSION * Client CTCP Reply * ``` <!-- github-sync-id:42598242 -->
adam closed this issue 2026-10-05 04:17:41 +02:00
Author
Owner

Was able to confirm on my live installation (running 1.5-nightly-20140509-3b01efc0).

Was able to confirm on my live installation (running 1.5-nightly-20140509-3b01efc0). <!-- github-comment-id:55365440 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#388