Security/WebAPI/Web Telephony: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 57: Line 57:
* probably would have broader implications
* probably would have broader implications
|-
|-
| 2||Attack from radio network||Malicious service provider or attacker with ability to inject radio packets could attack the web telephony stack.||* Code review * Fuzzing||Malicious service provider or attacker with ability to inject radio packets||?||?||?||||
| 2||Attack from radio network||Malicious service provider or attacker with ability to inject radio packets could attack the web telephony stack.||
* Code review  
* Fuzzing
||Malicious service provider or attacker with ability to inject radio packets||?||?||?||||
|-
|-
| 3||Bug in Web Telephony stack leads to code execution vulnerability ||A web page could supply malicious data to an API, triggering an exploitable crash.||* Code review* Fuzzing* Limiting access to API||Malicious web content||||||?||||
| 3||Bug in Web Telephony stack leads to code execution vulnerability ||A web page could supply malicious data to an API, triggering an exploitable crash.||
* Code review
* Fuzzing
* Limiting access to API
||Malicious web content||||||?||||
*Dangerous since it involves privileged code
*Dangerous since it involves privileged code
|-
|-
canmove, Confirmed users
1,220

edits

Navigation menu