09-11-2022 01:00 AM - edited 09-11-2022 01:33 AM
I found today in my 6500 core logs some user ip trying to log in to the core on port 443 even though i already have an access list for the authorized users under the vty lines which obviously didn't offer any protection against 443 attempt. so my question how can one try to log in to a switch through 443 port? as it is neither telnet or ssh port? and how was he able to bypass the vty lines access list?
here is one of the logs
%SEC_LOGIN-4-LOGIN_FAILED: Login failed [user:X] [Source: X] [localport: 443] [Reason: Login Authentication Failed - BadPassword]
Solved! Go to Solution.
09-11-2022 02:09 AM
443 = secure http(s) , whilst vty is related to terminal based access , you need to apply an ACL for that port (too)
M.
09-12-2022 08:54 AM - edited 09-12-2022 08:56 AM
Hmm, unsure a vty ACL can block https (or http).
You might want to disable, if enabled, i.e. "no ip http secure-server" (and "no ip http server"). You might also consider, enabling an ACL and/or access authorization for the http services (http ACL command mentioned by @Georg Pauwen), if you wish to use them at all. (See "ip http . . ." commands.)
09-11-2022 02:09 AM
443 = secure http(s) , whilst vty is related to terminal based access , you need to apply an ACL for that port (too)
M.
09-11-2022 04:51 AM
%SEC_LOGIN-4-LOGIN_FAILED: Login failed [user:X] [Source: X] [localport: 443] [Reason: Login Authentication Failed - BadPassword]
if you run HTTP server in SW, then this is DDoS I think, you need ACL
ip http access-class access-list-number
09-12-2022 03:47 AM
if im not using http and secure http for mgmt i think disabling should protect me from future attacks right?
09-12-2022 04:05 AM
Yes the port 443 for http.
09-12-2022 12:33 AM
Hello,
--> %SEC_LOGIN-4-LOGIN_FAILED: Login failed [user:X] [Source: X] [localport: 443]
Are 'user X' and 'source X' what actually appear in the log message, or did you edit this ?
09-12-2022 03:49 AM
i edited them for security. what can i do to protect my network from future attempts as the ip came from the local network , i already have acl for telnet and ssh
09-12-2022 09:19 AM
Hello,
you (obviously) should be able to track down the machine that was attempting to login. As well as whom the user ID belongs to,
09-12-2022 08:54 AM - edited 09-12-2022 08:56 AM
Hmm, unsure a vty ACL can block https (or http).
You might want to disable, if enabled, i.e. "no ip http secure-server" (and "no ip http server"). You might also consider, enabling an ACL and/or access authorization for the http services (http ACL command mentioned by @Georg Pauwen), if you wish to use them at all. (See "ip http . . ." commands.)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide