Cybersecurity

10036 readers

8 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Be respectful. Everyone should feel welcome here.
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
No Ads / Spamming.
No pornography.

Community Rules

Idk, keep it semi-professional?
Nothing illegal. We're all ethical here.
Rules will be added/redefined as necessary.

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !securitynews@infosec.pub !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 3 years ago

MODERATORS

kid@sh.itjust.works

Lanky_Pomegranate530@midwest.social

Weird server requests (lemmy.dbzer0.com)

submitted 2 months ago by WrenHavoc@lemmy.dbzer0.com to c/cybersecurity@sh.itjust.works

5 comments fedilink hide all child comments

So I'm the server admin and web developer for my school's robotics team. I look through the servers access logs every once in a while just to check on things. I keep seeing requests that look like someone's scanning for vulns. But I'm seeing something I've never seen before. It looks like someone is sending requests in machine code and I have no idea why or what it would do???

here's the request:

"\x03\x00\x00\x13\x0E\xE0\x00\x00\x00\x00\x00\x01\x00\x08\x00\x02\x00\x00\x00" 400 166 "-" "-"

top 5 comments

sorted by: hot top controversial new old

[–] jubilationtcornpone@sh.itjust.works 0 points 2 months ago (1 children)

Is the server exposed to the WAN? If so, what ports are forwarded to it? Do you know where these requests are coming from?

[–] WrenHavoc@lemmy.dbzer0.com 0 points 2 months ago* (last edited 2 months ago) (1 children)

Yeah, its running a website. All ports are on default deny except 22, 80, 443, and 9050. 9050 is for the onion version of the site, and 80 auto-redirects to the https version of the site. 22 is rate limited to help protect against brute-force attacks. The requests are coming from multiple IPs, some of them are 117.72.47.192, 172.71.184.89, and 162.158.87.100. the one that sent that specific packet is 82.147.85.33 and no user agent is provided. Most of the malicious packets have user agents attached, but that specific one doesn't I also am seeing another weird one sent by 138.197.16.14

"238\x00ll|'|'|SGFjS2VkX0Q3NUU2QUFB|'|'|WIN-QZN7FJ7D1O|'|'|Administrator|'|'|19-11-28|'|'||'|'|Win 10 Pro x64|'|'|No|'|'|S17|'|'|..|'|'|SW5ib3ggLSBPdXRsb29rIERhdGEgRmlsZSAtIE1pY3Jvc29mdCBPdXRsb29rAA==|'|'|" 400 166 "-" "-"

[–] thr0w4w4y2@sh.itjust.works 0 points 2 months ago (1 children)

they’re all attack attempts. set up fail2ban, disable ssh key-based authentication, run it in a non standard port and create firewall allow lists for trusted users, networks or countries if you can. make sure everything is patched frequently.

expect consequences for running onion hidden services - captchas and denied service for that IP address, but also attacks against the hidden service itself.

[–] willougr@lemmy.org 0 points 2 months ago

Probably best to keep the ssh key-based authentication...

[–] JRaccoon@discuss.tchncs.de 0 points 2 months ago* (last edited 2 months ago)

Probably just testing for some vulnerability. If you're current on patches, you can just disregard as background noice. If it really happens a lot, setting up something like Fail2ban would be useful.

Edit: A quick google search suggests it looks like a Windows Remote Desktop packet header. So something scanning the internet for machines with open RDP