this post was submitted on 18 Jun 2024
105 points (96.5% liked)

Cybersecurity

5689 readers
189 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

Community Rules

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 !cybersecurity@lemmy.capebreton.social !securitynews@infosec.pub !netsec@links.hackliberty.org !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 1 year ago
MODERATORS
 

A researcher has found a way to impersonate Microsoft corporate email accounts, which could make phishing attacks harder to spot.

top 6 comments
sorted by: hot top controversial new old
[–] pleasejustdie@lemmy.world 27 points 5 months ago* (last edited 5 months ago) (2 children)

My initial question was did this "researcher" just discover SMTP Open Relay? Cause if so I can do the exact same thing by configuring my SMTP server to open relay then using telnet to connect to it and issue the SMTP commands directly and it will send the email as though sent from whatever email address I want. This has been a known issue with SMTP for decades at this point and can't be reliably resolved with SMTP, but since the whole world uses it for email, its probably not going away any time soon. However to mitigate it as much as possible is what DMARC DNS entries are supposed to help with, by providing assurance that the email was sent by an SMTP server allowed to send email on behalf of the domain.

I used to send people emails from themselves to demonstrate why they can't trust the "from" address when they get an e-mail.

[–] stringere@sh.itjust.works 15 points 5 months ago (1 children)

However to mitigate it as much as possible is what DMARC DNS entries are supposed to help with, by providing assurance that the email was sent by an SMTP server allowed to send email on behalf of the domain.

+DKIM and SPF as long as we're naming email authentication methods.

[–] pleasejustdie@lemmy.world 7 points 5 months ago

yup, those too.

[–] IHawkMike@lemmy.world 8 points 5 months ago

Exactly. Show me the Authentication-Results header or gtfo.

[–] homesweethomeMrL@lemmy.world 13 points 5 months ago

“Microsoft just said they couldn’t reproduce it without providing any details,” Koroin told TechCrunch in an online chat. “Microsoft might have noticed my tweet because a few hours ago they reopen [sic] one of my reports that I had submitted several months ago.”

lol

[–] jemikwa@lemmy.blahaj.zone 7 points 5 months ago* (last edited 5 months ago)

The bug, according to Kokorin, only works when sending the email to Outlook accounts.

Sounds like it's something client side or specific to Microsoft's o365/outlook.com servers. Could be the exploit bypasses header verdicts for SPF/dkim/dmarc