[
https://bro-tracker.atlassian.net/browse/BIT-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21953#comment-21953
]
Gary Faulkner commented on BIT-1469:
------------------------------------
Sorry, let's try this again with snaplen set to 1514. bad-rdp-04SEP15-2.pcap
should have the full packet for the following alerts:
1441381279.831679 Cma3pM3jbrVTDV5Ev8 96.62.17.17 61206
xxx.xxx.64.242 3389 tcp RDP Binpac exception: binpac exception:
out_of_bound: DT_Data:application_type: 3 > 2
1441381310.466655 C0XEFADoqNaRk8P1h 96.62.17.17 63543
xxx.xxx.62.134 3389 tcp RDP Binpac exception: binpac exception:
out_of_bound: DT_Data:application_type: 3 > 2
1441381326.717656 Cfg1pMVWT81RwKF52 96.62.17.17 64869
xxx.xxx.193.242 3389 tcp RDP Binpac exception: binpac exception:
out_of_bound: DT_Data:application_type: 3 > 2
> dpd.log contains lots of binpac exceptions for RDP
> --------------------------------------------------
>
> Key: BIT-1469
> URL: https://bro-tracker.atlassian.net/browse/BIT-1469
> Project: Bro Issue Tracker
> Issue Type: Problem
> Components: BinPAC, Bro
> Affects Versions: git/master
> Environment: RHEL 6.6, 2.4-10 bro build from git
> Reporter: Gary Faulkner
> Labels: analyzer
> Fix For: 2.5
>
> Attachments: bad-rdp-04SEP15-2.pcap, bad-rdp-04SEP15.pcap,
> rdp-31AUG15.pcap
>
>
> RDP scanners seem to generate a lot of binpac errors in dpd.log for RDP
> connections.
> The following log line is an example of the error that repeats continuously
> during the activity:
> 1441031469.413008 CPNcey4q2i8mGVUvEg 74.91.23.83 62082
> 10.10.81.207 3389 tcp RDP Binpac exception: binpac exception:
> out_of_bound: DT_Data:application_type: 3 > 2
> The 10.x.x.x IP is the redacted local IP. The other IP is the scanner.
--
This message was sent by Atlassian JIRA
(v7.0.0-OD-02-259#70102)
_______________________________________________
bro-dev mailing list
[email protected]
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
