---
title: "Discussion on \"Account Takeover due to DNS Rebinding\" | Hashnode"
description: "Discussion on \"Account Takeover due to DNS Rebinding\". Hello guys, after a long time, I decided to write a blog post. I chose a vulnerability that I recently uncovered in Hashnode. As you may have already noticed, I set up this blog on Hashnode. Naturally, when I use a third-party service like this, I sp..."
url: "https://hashnode.com/posts/account-takeover-due-to-dns-rebinding/66e98ac1e42f1a7e03167b3b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Account Takeover due to DNS Rebinding](https://blog.voorivex.team/account-takeover-due-to-dns-rebinding?utm_source=hashnode&utm_medium=feed)

Hello guys, after a long time, I decided to write a blog post. I chose a vulnerability that I recently uncovered in Hashnode. As you may have already noticed, I set up this blog on Hashnode. Naturally, when I use a third-party service like this, I sp...

Sep 17, 2024 · 5 min read · blog.voorivex.team  
Updated Mar 2, 2025  
Read the article

-   [#dns-rebinding](https://hashnode.com/tag/dns-rebinding)
-   [#bugbounty](https://hashnode.com/tag/bugbounty)
-   [#account-takeover](https://hashnode.com/tag/account-takeover)

## Written by

[Voorivex](https://hashnode.com/@Voorivex)

@Voorivex

  
[View profile](https://hashnode.com/@Voorivex)

@yshahinzadeh

I work as an instructor and hunter, leading a small team to grow, learn, and innovate.

## Responses 3

Markdown supported · ⌘↵ to post

[rootface](https://hashnode.com/@root-face)

[Dec 29, 2025](https://hashnode.com/posts/account-takeover-due-to-dns-rebinding/66e98ac1e42f1a7e03167b3b/comment/69524bacb8011701c6335703)

cool

[VCODER](https://hashnode.com/@vc0d3r)

[Sep 17, 2024](https://hashnode.com/posts/account-takeover-due-to-dns-rebinding/66e98ac1e42f1a7e03167b3b/comment/66e995e471770e9a54e291d4)

nice writeup , thanks for sharing

I have a question : so if the `next_check()` checks (verify) the cname record every time (when function called) and if it matches "hashnode.network" it will prevent this attack ?

and the cause of this vulnerability is because hashnode only verifies the cname record once , only when it is adding to the db, , am I correct?🤔

[Voorivex](https://hashnode.com/@Voorivex)

[Sep 17, 2024](https://hashnode.com/posts/account-takeover-due-to-dns-rebinding/66e98ac1e42f1a7e03167b3b/comment/66e995e471770e9a54e291d4#reply-66e9a6ee24917bedfe9374da)

First question: yes, but the checker function should not rely on the DNS cache. If it does, the attack will still exist

Second question: not just once. Hashnode checked the DNS record at regular intervals (every 10 minutes) which was prone to DNS Rebinding attack

[Navid Mirzaaghazadeh](https://hashnode.com/@mirzaaghazadeh)

[Sep 17, 2024](https://hashnode.com/posts/account-takeover-due-to-dns-rebinding/66e98ac1e42f1a7e03167b3b/comment/66e98ebbc849e93855da086c)

<3