Slide 13 of 28
Part 2 · How It WorksSlide 13
Slide 13 · Real Incident
USPS Informed Delivery — an undocumented API exposed 60 million accounts.
November 2018. An API endpoint not in any documentation let authenticated users query any other user’s data.
📄 KrebsOnSecurity · November 2018
THE VULNERABILITY
USPS Informed Delivery — Undocumented API with No Authorization Check

The United States Postal Service’s Informed Delivery service allows users to see scans of their incoming mail. The service has an API that partners and internal systems use. Security researcher Brian Krebs reported in November 2018 that the API contained an endpoint that allowed any authenticated user to request data for any other account.

The endpoint was not in any public documentation. It was part of an internal/partner API that was accessible to all authenticated users — even those who should not have had access to other users’ data.

The API accepted queries for account data using parameters like email address or phone number, and returned: name, address, email address, phone number, mailing campaign data, and other account details for the queried user — regardless of whether the requesting user had any authorization to view that data.

Scale and impact: With approximately 60 million USPS.com accounts at the time, the undocumented API provided a mechanism to query personal information for any of those accounts. The vulnerability had been present for approximately a year before Krebs reported it. USPS had been notified by a researcher but did not act promptly — the issue was only fixed after Krebs published his report. The API9 aspect: The endpoint was not part of the documented, audited API surface. It was an undocumented endpoint that received none of the access control review applied to documented endpoints — a classic inventory management failure.
The undocumented endpoint problem

Undocumented endpoints are invisible to security reviews, penetration tests, and access control audits. They exist — but they’re not in scope for any security process because no one documented that they existed. Automated endpoint discovery and comprehensive API inventory are the only ways to bring them into scope.

← Back Attack Scenarios →