# Sensitive Information Exposure

**URL:** <https://devforum.zoom.us/t/sensitive-information-exposure/82860>\
**Category:** App Submission\
**Created:** [February 9, 2023, 5:01pm UTC](https://devforum.zoom.us/t/sensitive-information-exposure/82860 "2023-02-09T17:01:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmartin](https://avatars.discourse-cdn.com/v4/letter/b/e274bd/32.png) [@bmartin](https://devforum.zoom.us/u/bmartin)\
**Post date:** [February 9, 2023, 5:01pm UTC](https://devforum.zoom.us/t/sensitive-information-exposure/82860/1 "2023-02-09T17:01:20Z")

</div>

I am in the process of submitting my Zoom OAuth app, and in the security reviewing, the reviewer stated that my old version of the API is exposing sensitive information

The old version of the API creates new scheduled meetings on my Zoom account and using `custCreate` with a JWT app for all my end users by returning the `start_url` to the person who creates the meeting from my app and the `join_url` to whom ever the host sends it to.

The reviewer stated that the `zak` query param which is an encoded JWT, can be decoded to expose Zoom account information like `zm skm` in the headers and `uid` in the payload.

I have asked the reviewer that the `zak` is part of the `start_url` sent in the response of the meeting creating Zoom endpoint and it needs to be there so we can redirect the user who creates the meeting to Zoom as a meeting host.

And I am not sure what kind of bad things people can do with the decoded JWT. The reviewer takes a bit of time to reply, so that is why I am asking here. What should I do to unblock the reviewing progress ASAP? I need this app published ASAP, because I am running late on the deadline, so getting fast replies is really critical.

Please note that the reviewer has asked for the above details to my old API which is using the JWT app, and not the new API which is using the OAuth app, which is the one I am trying to publish.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [February 17, 2023, 10:14pm UTC](https://devforum.zoom.us/t/sensitive-information-exposure/82860/2 "2023-02-17T22:14:03Z")

</div>

Hi @bmartin  
Thanks for reaching out to the Zoom Developer Forum.  
Sorry for the late reply on this!  
Have you been able to communicate with your reviewer? If not, could you please share with me the name of your app and what is the status of your application?

Best,  
Elisa

---

<div class="post-metadata">

**Author:** ![bmartin](https://avatars.discourse-cdn.com/v4/letter/b/e274bd/32.png) [@bmartin](https://devforum.zoom.us/u/bmartin)\
**Post date:** [March 3, 2023, 2:12pm UTC](https://devforum.zoom.us/t/sensitive-information-exposure/82860/3 "2023-03-03T14:12:07Z")

</div>

I did yes, all resolved. Thank you and sorry for the late reply
