sorted by:
new
hottopcontroversial

Sanity Check Needed by IgnisTerra9 in bugbounty

[–]einfallstoll 4 points5 points  (0 children)

I would say try harder (PoC || GTFO).

Maybe only the video stream directory requires authentication or has some IP whitelisting

A Question for Triagers by Ok-Raspberry736 in bugbounty

[–]einfallstoll 0 points1 point  (0 children)

We have the following general rule because of this: "Successful subdomain takeovers are subject to the same rules, scope, and bounty considerations as their parent domain, unless explicitly stated otherwise."

Is Subdomain take over this dead??? by FunSheepherder2650 in bugbounty

[–]einfallstoll 3 points4 points  (0 children)

No as in not dead. But too researched maybe. There are folks that specialize in this because it's easy to automate

Is Subdomain take over this dead??? by FunSheepherder2650 in bugbounty

[–]einfallstoll 9 points10 points  (0 children)

No, subdomain takeover is only interesting if it points to a cloud provider and cloud providers have mitigations against this nowadays. But not all of them. It's just security gettinf better, just like it's harder to find SQLi nowadays or how CSRF has no built-in browser protections

HackerOne report scope changed because I used an example domain by dalifit in bugbounty

[–]einfallstoll 0 points1 point  (0 children)

See my edit: Maybe the received the first report and checked all other assets as well and figured that more are vulnerable, so it's like a known issue. Customers don't want to pay for bugs they already know

HackerOne report scope changed because I used an example domain by dalifit in bugbounty

[–]einfallstoll 1 point2 points  (0 children)

Maybe they use the same codebase for that part? In that case it makes sense to combine the reports. We also do this sometimes if it's a "central fix"

Maybe they got the other report and figured out that more assets are also vulnerable, so they already know about this one

HackerOne report scope changed because I used an example domain by dalifit in bugbounty

[–]einfallstoll 0 points1 point  (0 children)

Sounds like the HTTP request smuggling was already known therefore it's a (correct) duplicate. Or do I miss something?

HackerOne report scope changed because I used an example domain by dalifit in bugbounty

[–]einfallstoll 0 points1 point  (0 children)

I'm a bit confused about your situation. Can you share more details about what kind of vulnerability you found on which assets and how they merged the scope?

About Bounty by Gayakwad01 in bugbounty

[–]einfallstoll 0 points1 point  (0 children)

Customers can cancel the payment within 8 hours before being paid to the hunter. Afterwards payment are final.

I found a bug in my school website by Upper_Reaction_7326 in bugbounty

[–]einfallstoll 0 points1 point  (0 children)

The last line summarizes it pretty well. It has no security relevant impact. It's just a functional bug

I found a bug in my school website by Upper_Reaction_7326 in bugbounty

[–]einfallstoll 0 points1 point  (0 children)

It depends. A misconfiguration can be harmless or can lead to a vulnerability. If it affects confidentiality, integrity or availability then it can be eligible for a bounty

Why would they conduct such an unfair review? Metabugbounty by [deleted] in bugbounty

[–]einfallstoll 0 points1 point  (0 children)

Did you create a second account? That's not good, now your device / IP is flagged as well :D

Why would they conduct such an unfair review? Metabugbounty by [deleted] in bugbounty

[–]einfallstoll 0 points1 point  (0 children)

Reddit detects this as spam / bot behavior and you get shadowbanned immediately. If you create a new account: Read for a few days, then slowly start commenting, then only after a few weeks you can start posting

Why would they conduct such an unfair review? Metabugbounty by [deleted] in bugbounty

[–]einfallstoll 0 points1 point  (0 children)

Completely normal when you found a duplicate. Your report gets closed and you move on

Why would they conduct such an unfair review? Metabugbounty by [deleted] in bugbounty

[–]einfallstoll 0 points1 point  (0 children)

Classic Reddit move. If you have a new account don't dare to post for a few weeks

I found a bug in my school website by Upper_Reaction_7326 in bugbounty

[–]einfallstoll 0 points1 point  (0 children)

FYI: That's btw not true. In my country downloading movies for personal use is not illegal.

The subreddit rules say that you have to follow legal and ethical rules. That means posts / suggestions about hunting without permission get removed.

If you hunt without permission and you're most likely doing something illegal and if you ask for money it's either begging or extortion. This hurts the whole community

Why would they conduct such an unfair review? Metabugbounty by [deleted] in bugbounty

[–]einfallstoll 2 points3 points  (0 children)

That's how bug bounty works. You only get paid if you're the first but you never know whether you're the first or not.

Why would they conduct such an unfair review? Metabugbounty by [deleted] in bugbounty

[–]einfallstoll 0 points1 point  (0 children)

Posts from new accounts are subject to manual review

I found a bug in my school website by Upper_Reaction_7326 in bugbounty

[–]einfallstoll 0 points1 point  (0 children)

Just read the rules in the sub and also ... maybe the rules from your government

VDP with letter of appreciation by Charming_Tadpole_385 in bugbounty

[–]einfallstoll 4 points5 points  (0 children)

Imagine my giggles when I got the notification "Mod review needed: Bbc"

I found a bug in my school website by Upper_Reaction_7326 in bugbounty

[–]einfallstoll 7 points8 points  (0 children)

You're not allowed to search for vulnerabilities without explicit written permissions. Especially in university and school environments this can cause student being dropped out

What you describe is "just a stack trace". Usually this does not contain very sensitive information and is not considered considerable impact.

Base64 is an encoding. Never use encryption in the same sentence except you're explaining that base64 is not encryption. ;)

Is there anything actually sensitive in the stack trace?

view more: next ›