Hardcoded credentials

MonoCMS Blog 1.0 stores hard-coded admin hashes in the log.xml file in the source files for MonoCMS Blog. Hash type is bcrypt and hashcat mode 3200 can be used to crack the hash...

CVE-2020-25987

MonoCMS Blog 1.0 stores hard-coded admin hashes in the log.xml file in the source files for MonoCMS Blog. Hash type is bcrypt and hashcat mode 3200 can be used to crack the hash...

CVE-2020-25987

CVE-2020-25987 affects MonoCMS Blog 1.0. The issue arises from hard-coded admin hashes stored in log.xml within the MonoCMS Blog source, with the hash type bcrypt and hashcat mode 3200 cited as crackable. This can enable credential exposure or misuse if an attacker can access the log.xml contents...

PT-2020-16261

Name of the Vulnerable Software and Affected Versions MonoCMS Blog version 1.0 Description The issue concerns the storage of hard-coded admin hashes in the log.xml file within the source files of MonoCMS Blog. The hashes are of type bcrypt, and it is possible to use hashcat mode 3200 to crack the...

CVE-2020-25987: Insertion of Sensitive Information into Log File

MonoCMS Blog 1.0 stores hard-coded admin hashes in the log.xml file in the source files for MonoCMS Blog. Hash type is bcrypt and hashcat mode 3200 can be used to crack the hash...

MonoCMS Blog 1.0 - Arbitrary File Deletion (Authenticated)

Exploit Title: MonoCMS Blog 1.0 - Arbitrary File Deletion Authenticated Date: 2020-09-20 Exploit Author: Shahrukh Iqbal Mirza @shahrukhiqbal24 Vendor Homepage: https://monocms.com/download Software Link: https://monocms.com/download Version: 1.0 Tested On: Windows 10 XAMPP CVE: N/A Proof of...

Inadequate Encryption Strength

Overview In bcrypt npm package before version 5.0.0, data is truncated wrong when its length is greater than 255 bytes. Recommendation Upgrade to version 5.0.0 or later. References - https://nvd.nist.gov/vuln/detail/CVE-2020-7689 - https://github.com/kelektiv/node.bcrypt.js776 -...

Integer Overflow or Wraparound and Use of a Broken or Risky Cryptographic Algorithm in bcrypt

In bcrypt npm package before version 5.0.0, data is truncated wrong when its length is greater than 255 bytes...

GHSA-5WG4-74H6-Q47V Integer Overflow or Wraparound and Use of a Broken or Risky Cryptographic Algorithm in bcrypt

In bcrypt npm package before version 5.0.0, data is truncated wrong when its length is greater than 255 bytes...

Insecure Hash Function

bcrypt uses an insecure hash function. The data passed into the hash function is not properly hashed when its length is greater than 255 bytes...

bcrypt encryption problem vulnerability

bcrypt is a library used in Node.js for encrypting passwords. An encryption issue vulnerability exists in versions of bcrypt prior to 5.0.0. The vulnerability stems from a networked system or product that does not properly use the relevant cryptographic algorithm, resulting in content that is not...

PT-2020-19712

Name of the Vulnerable Software and Affected Versions bcrypt versions prior to 5.0.0 Description The issue occurs when data length exceeds 255 bytes, resulting in incorrect truncation. Recommendations For versions prior to 5.0.0, update to version 5.0.0 or later to resolve the issue...

Insecure Encryption

Overview bcrypt is an A library to help you hash passwords. Affected versions of this package are vulnerable to Insecure Encryption. Data is truncated wrong when its length is greater than 255 bytes. Remediation Upgrade bcrypt to version 5.0.0 or higher. References - GitHub Issue - GitHub PR 1 -...

Password Hashing: Do not use MD5

Impact User passwords are stored in the database using the rather outdated and cryptographically insecure MD5 hash algorithm. Furthermore, the hashes are salted using the username instead of a random salt, causing hashes for users with the same username and password to collide which is problemati...

GHSA-H362-M8F2-5X7C Password Hashing: Do not use MD5

Impact User passwords are stored in the database using the rather outdated and cryptographically insecure MD5 hash algorithm. Furthermore, the hashes are salted using the username instead of a random salt, causing hashes for users with the same username and password to collide which is problemati...

CVE-2020-5229

Opencast before 8.1 stores passwords using the rather outdated and cryptographically insecure MD5 hash algorithm. Furthermore, the hashes are salted using the username instead of a random salt, causing hashes for users with the same username and password to collide which is problematic especially...

CVE-2020-5229

Opencast before 8.1 stores passwords using the rather outdated and cryptographically insecure MD5 hash algorithm. Furthermore, the hashes are salted using the username instead of a random salt, causing hashes for users with the same username and password to collide which is problematic especially...

Default credentials

Opencast before 8.1 stores passwords using the rather outdated and cryptographically insecure MD5 hash algorithm. Furthermore, the hashes are salted using the username instead of a random salt, causing hashes for users with the same username and password to collide which is problematic especially...

CVE-2020-5229

Opencast before 8.1 stores passwords using the rather outdated and cryptographically insecure MD5 hash algorithm. Furthermore, the hashes are salted using the username instead of a random salt, causing hashes for users with the same username and password to collide which is problematic especially...

CVE-2020-5229

Opencast before 8.1 stores passwords using the rather outdated and cryptographically insecure MD5 hash algorithm. Furthermore, the hashes are salted using the username instead of a random salt, causing hashes for users with the same username and password to collide which is problematic especially...