bnamed.net Cross Site Request Forgery vulnerability

2019-11-26T11:15:00
ID OBB:1023915
Type openbugbounty
Reporter Auntor
Modified 2019-12-26T11:15:00

Description

Open Bug Bounty ID: OBB-1023915

Security Researcher Auntor Helped patch 43 vulnerabilities
Received 3 Coordinated Disclosure badges
Received 3 recommendations
, a holder of 3 badges for responsible and coordinated disclosure, found a security vulnerability affecting bnamed.net 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:| bnamed.net
---|---
Open Bug Bounty Program:| View Open Bug Bounty Program
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:| Auntor Helped patch 43 vulnerabilities
Received 3 Coordinated Disclosure badges
Received 3 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:bnamed.net  vulnerability

Screenshot After CSRF:bnamed.net  vulnerability

Coordinated Disclosure Timeline

Vulnerability Reported:| 26 November, 2019 11:15 GMT
---|---
Vulnerability Verified:| 27 November, 2019 07:36 GMT
Website Operator Notified via Bug Bounty:| 27 November, 2019 07:36 GMT
Public Report Published
[without any technical details]:| 27 November, 2019 07:36 GMT
---|---
Vulnerability Fixed:| 4 December, 2019 09:05 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.| 26 December, 2019 11:15 GMT
---|---