CVE-2021-45892
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in Softwarebuero Zauner ARC 4.2.0.4. There is storage of Passwords in a Recoverable Format.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Softwarebuero Zauner ARC 4.2.0.4 application stores user passwords in a recoverable format rather than using proper cryptographic hashing. This means passwords are either stored in plaintext or using reversible encryption, allowing attackers who obtain access to the password database to recover the original credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.2.0.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm installed version of Zauner ArcLocate the application version through the software itself (about dialog, help menu) or check installation/manifest files for version metadataAffected if Version is exactly 4.2.0.4
-
Identify password storage locationFind where Zauner Arc stores user credential data - this is typically a database file, user configuration directory, or backend data store used by the applicationAffected if Version is 4.2.0.4 and password storage location can be located
-
Examine stored password formatOpen or query the password storage and inspect how credentials are stored - look at whether passwords appear as readable text, encoded strings, or encrypted blobs that could be reversed to plaintextAffected if Passwords are stored in plaintext, base64-encoded, or use reversible encryption rather than cryptographic hashes
-
Verify hashing mechanism is absentCheck if stored passwords use proper key derivation functions (bcrypt, scrypt, Argon2) - these produce irreversible hashes; if passwords can be converted back to plaintext, proper hashing is not in useAffected if Passwords are stored in any recoverable format that allows recovery of the original plaintext credentials
If the installed version is 4.2.0.4 and passwords are stored in plaintext, base64, or any reversible encryption format instead of irreversible hashed values, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper password hashing using a strong, salted key derivation function such as bcrypt, scrypt, or Argon2, and migrate existing passwords to the new secure format.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45892 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-45892 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data