\n
I spend a lot of time talking about the value of good API documentation.
\nIf you ever encounter a target API developed by a team that publishes detailed API documentation following the OpenAPI Specification (OAS), youβre in the money baby.
\nIn this week's article, I show you how to weaponize the tools developers use against them to find potential attack vectors in the very APIs they are building and documenting.
\nYou'll have to read the article to see how.
\nREAD ARTICLE. WEAPONIZE. EXPLOIT. |
Here is a glimpse of the articles I wrote last month that you received through the weekly newsletters...
\n1οΈβ£ You were given The Beginners Guide to Writing API Security Tests in Postman, where you learned everything you need to know about how to get started writing API security tests in Javascript using Postman.
\n2οΈβ£ I showed you how to Break APIs with Naughty Strings, using nothing more than a nasty wordlist and the Postman Collection Runner.
\n3οΈβ£ You got to experience what I went through as I answered the question \"Is Bruno a good Postman alternative for API hacking?\" (spoiler - It's not... yet)
\n4οΈβ£ I shared with you five tips to help you pick your first target when starting bug bounty hunting against APIs.
\nWishing I'd cover something else? Just hit \"reply\" on this email and let me know. It might be considered for a future article!
\nThis week's pro tip comes from Cristi over on X.
\nWith the latest release of Burp Suite, you can now have it automatically filter out uninteresting headers in requests. This setting can be found in the User Interface settings for your User profile.
\nSo what does it do?
\nBy default, Burp shows all headers when you view HTTP requests in the message editor. To change this in the Pretty tab for HTTP requests across Burp, select Hide uninteresting headers by default. That's the little eye icon above the request.
\nThis setting turns that on by default.
\nBurp hides a predefined list of headers that typically offer little insight into the target application's behavior or contain information that can't be exploited, such as Sec-Ch-Ua, Accept-Language, and Upgrade-Insecure-Requests.
\nBy filtering uninteresting headers out, you can reduce clutter, making it easier for you to focus your analysis on more valuable information.
\nThanks for the tip Christi!
\nπ€ SmartBear has revealed how it is elevating API development with its acquisition of Stoplight. They share how they have integrated Spectral into SwaggerHub, and how an upcoming release also integrated Prism for HTTP mocking and proxying.
\nπ οΈ Have you heard about Compass Security's new JWT-scanner Burp extension? It automates the testing of JSON Web Token (JWT) implementations in web apps and APIs. I thought the JWT JWK injection testing was a nice touch. GitHub repo is here. It's also in the BApp store.
\nπ Circular dependencies suck. Especially when it happens in an API that takes down the entire app like Tencent Cloud recently saw that took WeChat offline. Ouch.
\nπ I read an interesting article on how API Design Is Pretty Bad β Hereβs How to Fix It. The fix-it part was interesting, as the article explains what developers SHOULD be doing. Of course, we can look at that with an offensive security engineering eye, and craft our methodologies accordingly.
\nπ° Have you been following the news about CVE-2024-3400? Wallarm does a decent job of discussing how Palo Alto Networks' API Exploit is Causing Critical Infrastructure and Enterprise Epidemics. Time to upgrade and patch if you are running Palo Alto Networks PAN-OS software.
\nπ Truffle Security has an awesome article on how (The) Postman Carries Lots of Secrets. They estimate over 4,000 live credentials are currently leaking publicly on Postman for a variety of popular SaaS and cloud providers. The article also introduces the fact that trufflehog can now scan Postman workspaces to look for credential exposure.
\nπ¬ The API Kitchen has a fun video on Mastering the OWASP ASVS (with Tanya Janca). Always interesting to see people talking about API stuff in the kitchen π€£
\nπ Did you check out Akamai's whitepaper on the 8 Do's & Don'ts of API Security? I found it kinda disappointing. Same old, same old. Why share it then? Because while it should be old hat to you by now... to some readers it's still rather new.
\nβ οΈ Have you ever wanted to backdoor a dotNet application? This article shows you how. It also introduces dnSpyEx, an unofficial continuation of dnSpy which lets you edit and debug dotNet assemblies. Don't be evil. Fair game for redteamers with a foothold on a box.
\nπ¨ββοΈ The US House of Representatives approved a bill that would limit the government's ability to purchase data from third parties. Called \"The Fourth Amendment is Not For Sale\", it makes it illegal for the US government to buy your data without a warrant. If you have read Means of Control, you know why this is important.
\nWell, that's it for this monthly review. With May now upon us, I know some of you will be out there wearing some Star Wars swag and telling everyone that \"May the 4th be with you\".
\nIt is Star Wars Day after all.
\nI have another idea for May 4th. Grab some milk. Maybe those Churro Oreos. Or perhaps gingerbread is more your thing...
\n\"May the milk be with you... always\"
\nTalk to you in the next newsletter. *burp*
\nHack hard!
Dana
\n |
| \n\n |
Helping developers, testers, and hackers improve their approach to appsec and find vulnerabilities in their apps and APIs before their adversaries do. Interested to know more? Subscribe to my newsletter below!
|
Helping developers, testers, and hackers improve their approach to appsec and find vulnerabilities in their apps and APIs before their adversaries do. Interested to know more? Subscribe to my newsletter below!