kono.store Cross Site Request Forgery vulnerability

2019-06-18T11:21:00
ID OBB:861614
Type openbugbounty
Reporter calv1n
Modified 2019-07-18T11:21:00

Description

Security Researcher calv1n Helped patch 22043 vulnerabilities
Received 12 Coordinated Disclosure badges
Received 37 recommendations
, a holder of 12 badges for responsible and coordinated disclosure, found a security vulnerability affecting kono.store website and its users.

Following coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has:

&nbsp&nbsp&nbsp&nbsp&nbsp&nbspa. verified the vulnerability and confirmed its existence;
&nbsp&nbsp&nbsp&nbsp&nbsp&nbspb. notified the website operator about its existence.

Affected Website:| kono.store
---|---
Open Bug Bounty Program:| Create your bounty program now. It's open and free.
Vulnerable Application:| Custom Code
Vulnerability Type:| CSRF (Cross-Site Request Forgery) / CWE-352
CVSSv3 Score:| 8.8 [CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H]
Disclosure Standard:| Coordinated Disclosure based on ISO 29147 guidelines
Discovered and Reported by:| calv1n Helped patch 22043 vulnerabilities
Received 12 Coordinated Disclosure badges
Received 37 recommendations

Remediation Guide:| OWASP CSRF Prevention Cheat Sheet
Export Vulnerability Data:| Bugzilla Vulnerability Data
JIRA Vulnerability Data [ Configuration ]
Mantis Vulnerability Data
Splunk Vulnerability Data
XML Vulnerability Data [ XSD ]

Vulnerable URL:

Research's Comment:

Screenshot Before CSRF:kono.store  vulnerability

Screenshot After CSRF:kono.store  vulnerability

Coordinated Disclosure Timeline

Vulnerability Reported:| 18 June, 2019 11:21 GMT
---|---
Vulnerability Verified:| 18 June, 2019 11:35 GMT
Website Operator Notified:| 18 June, 2019 11:35 GMT
a. Using the ISO 29147 guidelines|
---|---
b. Using publicly available security contacts|
c. Using Open Bug Bounty notification framework|
d. Using security contacts provided by the researcher|
Public Report Published
[without any technical details]:| 18 June, 2019 11:35 GMT
Vulnerability Fixed:| 29 June, 2019 21:44 GMT
---|---
Public Disclosure: A security researcher can delete the report before public disclosure, afterwards the report cannot be deleted or modified anymore. The researcher can also postpone public disclosure date as long as reasonably required to remediate the vulnerability.| 18 July, 2019 11:21 GMT
---|---