Following the coordinated and responsible vulnerability disclosure guidelines of the **[ISO 29147]()** standard, Open Bug Bounty has:
a. verified the vulnerability and confirmed its existence;
b. notified the website operator about its existence.
Technical details of the vulnerability are currently hidden (“On Hold”) to give the website operator/owner sufficient time to patch the vulnerability without putting any of its systems or users at risk. Once patched, vulnerability details can be publicly disclosed by the researcher in at least 30 days since the submission. If for a reason the vulnerability remains unpatched, the researcher may disclose vulnerability details only after 90 days since the submission.
Affected Website:| **[cylinder.no]() **
Open Bug Bounty Program:| **Create your bounty program now**. It’s open and free.
Vulnerable Application:| [hidden until disclosure]
Vulnerability Type:| **[IAC (Improper Access Control)]()** / CWE-284
CVSSv3 Score:| [hidden until disclosure]
Disclosure Standard:| Coordinated Disclosure based on **[ISO 29147]()** guidelines
Discovered and Reported by:| **Gh05tPT **
Remediation Guide:| **[OWASP Access Control Cheat Sheet]()**
### Coordinated Disclosure Timeline
Vulnerability Reported:| 15 March, 2023 14:38 GMT
Vulnerability Verified:| 15 March, 2023 14:50 GMT
Website Operator Notified:| 15 March, 2023 14:50 GMT
a. Using the ISO 29147 guidelines| !(/images/done.png)
b. Using publicly available security contacts| !(/images/done.png)
c. Using Open Bug Bounty notification framework| !(/images/done.png)
d. Using security contacts provided by the researcher| !(/images/done.png)
Public Report Published [without technical details]:| 15 March, 2023 14:50 GMTRead More
Back to Main