Skip to content

Commit 689e243

Browse files
authored
Update 0xa3-excessive-data-exposure.md
1 parent 71ecbc2 commit 689e243

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

2019/en/src/0xa3-excessive-data-exposure.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,16 @@ comment’s author, is also returned. The endpoint implementation uses a generic
2323
`toJSON()` method on the `User` model, which contains PII, to serialize the
2424
object.
2525

26+
### Scenario #2
27+
28+
An IOT-based surveillance system allows administrators to create users with different permissions.
29+
An admin created a user for a new security guard that should have access only to specific buildings in the site.
30+
Once the security guard uses his IPAD, an API call is triggered to:
31+
"/api/sites/111/cameras" in order to receive data about the available cameras and show them on the dashboard.
32+
The response contains a list with details cameras in the following format:
33+
{"id":"xxx","live_access_token":"xxxx-bbbbb","building_id":"yyy"}
34+
While the client GUI shows only cameras the security guard should have access to, the actual API response contains a full list of all the cameras in the site.
35+
2636
## How To Prevent
2737

2838
* Never rely on the client side to perform sensitive data filtering.

0 commit comments

Comments
 (0)