 |
|
 |
 |
Menu |
 |
|
 Home |
| |
|
 Discussions |
| |
|
 Tools |
| |
|
| Affiliates |
| |
|
 Content |
| |
|
 Info |
| | |
|
|
|
|
|
User Info |
|
 Membership:
 Latest: MichaelSnaRe
 New Today: 0
 New Yesterday: 0
 Overall: 9144
 People Online:
 Visitors: 302
 Members: 0
 Total: 302
|
|
|
|
|
|
Full disclosure |
|
CyberDanube Security Research 20251014-0 | Multiple Vulnerabilities in Phoenix Contact QUINT4 UPS
apis.google.com - Insecure redirect via __lu parameter(exploited in the wild)
Urgent Security Vulnerabilities Discovered in Mercku Routers Model M6a
Re: Security Advisory: Multiple High-Severity Vulnerabilities in Suno.com (JWT Leakage, IDOR, DoS)
Security Advisory: Multiple High-Severity Vulnerabilities in Suno.com (JWT Leakage, IDOR, DoS)
[SBA-ADV-20250730-01] CVE-2025-39664: Checkmk Path Traversal
[SBA-ADV-20250724-01] CVE-2025-32919: Checkmk Agent Privilege Escalation via Insecure Temporary Files
CVE-2025-59397 - Open Web Analytics SQL Injection
Re: [FD]Full Disclosure: CVE-2025-31200 & CVE-2025-31201 – 0-Click iMessage Chain ? Secure Enclave Key Theft, Wormable RCE, Crypto Theft
Re: Full Disclosure: CVE-2025-31200 & CVE-2025-31201 – 0-Click iMessage Chain ? Secure Enclave Key Theft, Wormable RCE, Crypto Theft
Re: Defense in depth -- the Microsoft way (part 93): SRP/SAFERwhitelisting goes black on Windows 11
Re: [FD]: "Glass Cage" – Zero-Click iMessage ? Persistent iOS Compromise + Bricking (CVE-2025-24085 / 24201, CNVD-2025-07885)
Re: [FD]Full Disclosure: CVE-2025-31200 & CVE-2025-31201 – 0-Click iMessage Chain ? Secure Enclave Key Theft, Wormable RCE, Crypto Theft
Samtools v1.22.1 Uncontrolled Memory Allocation from Large BED Intervals Causes Denial-of-Service in Samtools/HTSlib
Samtools v1.22.1 Improper Handling of Excessive Histogram Bin Counts in Samtools Coverage Leads to Stack Overflow
|
|
|
|
|
|
 |
|
 |
 |
|
 |
IT Security and Insecurity Portal |
|
 Posted: Tue Dec 23, 2008 3:04 am |
 |
|
| FreakOnALeach |
| Beginner |
 |
|
| Joined: Dec 23, 2008 |
| Posts: 1 |
|
|
|
 |
|
 |
|
0d858a7dbf9b5c395f326995182d2658:HMGLJ
Wouldn't ask, if I had the capabilities to do it on my own... 
Thanks in advance! |
|
|
|
|
|
|
|
|
| Posted: Tue Dec 23, 2008 4:31 am |
|
|
| tehhunter |
| Valuable expert |
|
|
| Joined: Nov 19, 2008 |
| Posts: 261 |
|
|
|
|
|
|
|
| Chb wrote: | | cusco wrote: | hi! I posted this in the md5-hases-help thread but I should have posted it here insead:
Hash: 3434f9b82292dc4ce442ebc7c0e73e42
Salt: $)*hf
How do you unsalt it? I have John running on the md5 hash, but I don't understand the use of the salt |
You actually aren't able to "unsalt" something. Salting means, that the salt changes the way of encryption. In case of DES for example, it changes the initialization-parameters of the algorithm (if I recall right), in case of MD5 it is mostly in front of the password.
Little example:
Password: bar
Salt: foo
Password to hash: foobar
So if you want to crack the hash, you'll have to put "foo" in front of the password you're trying. |
That's not exactly right. Salting means that there is an extra level of security thrown into the hashing process so that, in the event of retrieving some passwords from a forum or something else, it is much harder to crack the passwords.
Example: 5d41402abc4b2a76b9719d911017c592 -> hello
You can try googling this hash and you will almost certainly find it in its unhashed form. Not hard right?
Now try: 2c2280813654075fed0b359d12856099
You can't right this online if you google it, though the password inside of it is still 'hello'. Why? Because I hashed the password twice, the second time with a certain small string on the end (e.g. the salt). This is how vBulletin hashes it's passwords in its databases.
The only way to unhash a salted password is to a) know the salt and b) know the salting scheme.
Invision Power Salt Scheme: MD5(MD5(salt).MD5(password))
vBulletin Salt Scheme: MD5(MD5(password).salt)
etc...
So then to decrypt them you have to account for these factors and then run a program to hash 'test' passwords in the same manner and check to see if the hash then is equal to the one you have. If it is, you have found a 'collison', and thus, the password.*
* In exceedingly rare circumstances, a collison may not be the password but rather another string combination that produces the same hash. |
|
|
|
|
|
www.waraxe.us Forum Index -> All other hashes
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
All times are GMT
Page 2 of 2
Goto page Previous1, 2
|
|
|
|
Powered by phpBB © 2001-2008 phpBB Group
|
|
|
|
|
|
|
