Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide sandbox of private access warnings #30

Open
trombonehero opened this issue May 16, 2015 · 1 comment
Open

Provide sandbox of private access warnings #30

trombonehero opened this issue May 16, 2015 · 1 comment

Comments

@trombonehero
Copy link
Member

Currently, SOAAP's private_access warnings tell us what sandbox the data being accessed was supposed to belong to (with the sandbox_private) field. I would also like to know what sandbox the access actually occurred in.

@trombonehero
Copy link
Member Author

It would be great if the representation for this could be consistent with what we do in a vulnerability_warning, i.e.:

{
  "function": "_ZNK6SkMask16computeImageSizeEv",
  "sandbox": "capsicum",     // or, as would often be the case, "sandbox": null
  "location": {
    "file": "../../third_party/skia/src/core/SkMask.cpp",
    "line": 23
  },
  /* ... */
  "trace_ref": "!trace0"
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant