@win3zz I don't think there is any impact here right? As there is no sensitive information as such.
I agree that it is leaking some info, but not sensitive as such.
Day 1:
Attackers typically take the below path to attack the organizations:
Reconnaissance -> Identify weakness -> Initial access by exploiting -> Persistence -> Credential access -> Lateral movement -> Command & Control
#hacking#redteaming#hackerhumble
JWT Token Bypasses #2:
1. Capture the JWT token.
2. If the algorithm is RS256 change to HS256 and sign the token with the public key (which you can get by visiting jwks Uri / mostly it will be the public key from the site's https certificate) (1/2)
#bugbountytips#bugbounty
@harshbothra_ O is for Open URL Redirect
The attacker injects the malicious URL typically in the trusted site request params which redirect the user to a malicious site.
Devs out there - Validate the URL before redirecting and if needed show a confirmation.
#security#atozofinfosec
@harshbothra_ S is for Subdomain takeover. This happens when there is a dangling subdomain and a CNAME is still pointed to the subdomain which is no longer in use.
Devs out there - Do not forget to remove CNAMEs when you deprovision a subdomain
#security#atozofInfoSec
@harshbothra_ B is for Broken Access Control
This happens when there is an IDOR / Privilege escalation.
Devs out there - Do not trust user input. Always validate who is the user and what he is trying to access.
#security#atozofinfosec
@harshbothra_ X is for XML External Entity Injection (XXE). When untrusted XML entities are resolved it can lead to Remote code execution.
Devs out there - Disable Entity resolving. If needed resolve only after proper validation and never load DTDs from untrusted servers.