this post was submitted on 04 Dec 2024
25 points (100.0% liked)

Cybersecurity

8117 readers
74 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 !securitynews@infosec.pub !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] Shadow@lemmy.ca 4 points 8 months ago* (last edited 8 months ago) (4 children)

I feel like this doesn't explain a lot. What makes it so trivial to find the origin? They just brush it aside as easy.

Also this really just comes back to: secure your origins folks, especially if you're relying on edge security features. Nobody should be relying on a waf though.

[โ€“] lemmyng@lemmy.ca 4 points 8 months ago

This means that when a CDN service is used as a WAF, the web application it protects is open to Internet traffic, and is expected to validate that it responds only to web traffic that originates from and by the CDN service.

When this validation is lacking, backend applications can easily be directly accessed over the Internet.

So, misconfigured backends that don't limit access to CDN sources can be fingerprinted through web scans. Seems like a big honking nothing-burger.

load more comments (3 replies)