Excessive data exposure meaning, in plain words

Excessive data exposure is an API flaw that returns more data than needed. How the OWASP API Security Top 10 (2019) explains it, and its merger into API3:2023.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

Excessive data exposure is a flaw in which an API returns more information than needed. An API is the window through which a smartphone app or a screen receives data from a server. In the explanation in the OWASP API Security Top 10 (2019 edition), the API returns sensitive data as it is by design and expects the screen side to narrow it down.

How does excessive data exposure work?

Imagine being asked for one postal code and handing over the whole address book in an envelope, so that the person who receives it reads only the one line they need. The envelope you handed over holds everyone else's addresses too.

With an API too, the screen may show only a name, while the content of the communication includes phone numbers and internal-use items. OWASP points out that if the communication is watched, that information can be read as it is. It also explains that when building a general-purpose window, developers may publish it without thinking about how sensitive the information is.

As a measure, OWASP recommends avoiding general-purpose conversion functions such as to_json() and choosing the items to return one by one. The free URL check reads only the public page, robots.txt, DNS and encryption information, so it does not show what an API returns. For a look at how your API responds, contact us.

Why does excessive data exposure matter?

Behind a smartphone app or a member site there is usually an API. Even if the screen looks plain, if the window behind it returns a lot of information, that information may be read from the communication.

OWASP explains that automated tools easily miss this problem. Whether information is legitimate or sensitive is hard to judge without knowing what is inside the app. In the 2023 edition, this item was merged into API3, "Broken Object Property Level Authorization".

The operator's review is to check, API by API, whether each item returned is really needed. The direction OWASP shows is to start by finding the APIs that return personal information, decide the shape of responses, and then verify that responses do not depart from the decided shape.

Related terms

Next step

The points to check are gathered on the excessive data exposure vulnerability page. The free URL check shows what is visible from outside, and you can talk through a review of your API in a free consultation.

Frequently asked questions

Can items that are not shown on the screen not be seen?

They may be seen. The content of the communication also arrives with items the screen does not show. OWASP asks that narrowing down the information not be left to the client side.

How should we decide which items to return?

Return only the items the other side uses, choosing them one by one. Classify personal and internal-use items, and review the responses of every API that returns them. OWASP also lists checking the shape of responses against a schema.

Frequently asked questions

Can items that are not shown on the screen not be seen?

They may be seen. The content of the communication also arrives with items the screen does not show. OWASP asks that narrowing down the information not be left to the client side.

How should we decide which items to return?

Return only the items the other side uses, choosing them one by one. Classify personal and internal-use items, and review the responses of every API that returns them. OWASP also lists checking the shape of responses against a schema.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.