The mods might…
Erm, just for the record: there were also non-mods (aka “regular users”) voting with the same close-reason. So, this wasn’t a case of mods being a bit hasty. It was a community-votes result.
The Question
Anyway, let’s look at the question itself:
I have this RSA public key
-----BEGIN PUBLIC KEY-----
MIIBIDANBgkqhkiG9w0BAQEFAAOCAQ0AMIIBCAKCAQEAx9a8pYAiNaVt9PrwjQ+0
cB6elLiGpcPQxkQckuPToObXVJcg2BSWG1M4XcH70oI3sCipPBDQiy1HvzHIvW96
qAYsbXR5ouEnNNF9hRlV3hE4LPQhN/H8QIOd8lYrepHcO2dR9gYM6zCQg312C3SJ
l6Q6AZGaDI8saxv7cmU95wqK4ZfrHGeAp1kUzaz5rKVq81BZtyhYTpuyhMR5Hoz+
0XPsZB58xbJ4/2gAhrk0wKuy7B9DGx0hc+rJcBn/UQCwtRD8h/9HoH58dI9nx2jX
3XOa3919CC6TPWA4ylVPMoLXqpByAo9DU9vvUVuOtv9YZ8A54b0fgHoMvtRlWGIG
DwIBAw==
-----END PUBLIC KEY-----
From which I get the values of n and e
n = 25227313400403003289291316040964706793284526130307773148182567990181812103363366492141868094341253168514098087977707768352520652692143206065406906643084095767849329466558935239586943914389925429616795559049929569740742883151498832979927915567828657543757871650853272541594015354947860164753295474118247326770430739348498870310114642065925503324951264351013482315725877175994479883134119470270775988034913135302127722176827339225792610659723969082753807504414521250872063048608812550101510336558064093636352586121260624931803298322088622685800438189865267661921807764104595582348335380035988782396542471100276681082383
e = 3
I have given a chipher.bin file which i have to decrypt using these values. I had tried to find the prime factor of n but failed, then I come to know about cube-root RSA attack but didn't able to figure out how to proceed.
To me, this translates to:
I’ve got an encrypted file and want to decrypt it using the above mentioned RSA key and known e and n values. How do I attack this key to decrypt my bin file? I’m not saying where, but I heard about something called “cube-root RSA attack”. As I don’t understand it and have even less of an idea how I would go about actually applying it, I need someone to hold my hand and walk me through this attack from A to Z, practically attacking/breaking the mentioned key.
Even now, this practically boils down to a request for analyzing and attacking an RSA key to me. That was the reason I regarded this – among other people – to be off-topic and voted accordingly.
If you check the comments, you’ll notice others didn’t go that far an interpreted the question to be a simple request to decrypt the bin file itself…
Now, I do understand what you are aiming at, but I fail to really see it in this case. See, it would have been a totally different case if the question would have been something along the lines of:
Hi, I’m trying to figure out how to actually apply a “cube-root RSA attack”. I have done the following research ... and know that ... but when I tried ... I failed to apply the attack successfully. What am I missing or doing wrong?
But when you re-read the quoted question, you’ll have to agree that it strongly differs from that since…
All that has been posted is the key, the e and n value and a request asking how to attack and break the key with the goal to decrypt some unknown file.
As said, I did (and still do) regard that to be a specific request for analyzing and attacking an RSA key and not a general question about “cube-root RSA attacks” which would be helpfull to others.
Your Re-Open Request
Nevertheless, as you have been able to provide an answer which obviously adds some of the value the question itself is lacking, I have decided to re-open the question as you requested.
Yet – should community votes close this question again – I won’t step in to rescue it once more.
Notice: To prevent future references from pointing here for the wrong reasons, I would like to point out and put an emphasis on the fact that the re-opening of this specific, individual question does not mean any or all alike (let’s just call them) “borderlining questions” can or should generally be considered to be on-topic. This is not a Carte Blanche / Blank Cheque to circumvent or undermine any of the well-vetted rules layed out in the Crypto.SE help center.