Menu

🧟 Old API Versions: Find the /v1 That Never Died, Then Prove It
πŸ“°

🧟 Old API Versions: Find the /v1 That Never Died, Then Prove It

DEV Community: appsecΒ·Krishna KumarΒ·3 days ago
#RSlCKqIo
#devtoappsec#devto#dev#version#reads
Reading 0:00
15s threshold

Teams ship /api/v2 , fix the authorization bug that /v1 had, update the docs, and move on. The router never got the memo. /api/v1/orders/1002 still answers, it still talks to the same database, and it still has the bug.

That's the whole idea behind OWASP's API9:2023 Improper Inventory Management : you can't secure an API version you've forgotten you run. This post is about finding those forgotten versions and hosts, and then doing the part that matters: proving, with your own test accounts, whether the old door actually skips a check the new one enforces.

Only test what you own or are explicitly authorized to test. Everything below uses stand-in hosts ( api.example.com ) and test accounts.

What API9 actually says

The OWASP entry describes attackers getting in through old API versions or endpoints that were left running unpatched with weaker security requirements.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.