This Endpoint Was “Read-Only” — Until I Read Everything
描述了一次深夜的安全侦察行动,利用自动化工具收集目标域的存活URL和API路径,揭示了开发者与实际生产环境中API权限配置的潜在问题。 2026-1-12 13:25:39 Author: infosecwriteups.com(查看原文) 阅读量:0 收藏

Iski

Free Link 🎈

Hey there!😁

Press enter or click to view image in full size

Image by AI

Ever noticed how life says “just look, don’t touch”… and then hands you the keys?

APIs do the same thing.

Developers say “read-only”, security teams nod, and somewhere in production a server quietly whispers, “take it all.” 😌

This is one of those nights.

How This Started (a.k.a. Another Late Recon Night)

It was past midnight. Coffee was cold. Tabs were multiplying. You know the drill.

I wasn’t chasing anything fancy — just running mass recon and letting endpoints show their personality.

subfinder -d target.com -all | httpx -silent > alive.txt

Then the usual URL soup:

cat alive.txt | waybackurls | gau | sort -u > urls.txt

While skimming through the output, a pattern kept showing up:

/api/v1/public/
/api/v2/read/…

文章来源: https://infosecwriteups.com/this-endpoint-was-read-only-until-i-read-everything-c157154bdb99?source=rss----7b722bfd1b8d---4
如有侵权请联系:admin#unsafe.sh