CVE-2021-41067
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 Listary through 6. Improper implementation of the update process leads to the download of software updates with a /check-update HTTP-based connection. This can be exploited with MITM techniques. Together with the lack of package validation, it can lead to manipulation of update packages that can cause an installation of malicious content.
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 · high confidenceListary through version 6 uses an insecure HTTP-based /check-update connection for software updates, allowing attackers on the same network to perform man-in-the-middle (MITM) attacks. Combined with the lack of cryptographic package validation, this enables injection of malicious update packages that get installed with elevated privileges.
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<= 6CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Check if Listary is installed and identify versionOpen Programs and Features (Windows) or check the installation directory for Listary. Look for the installed version number in the application properties or about dialog.Affected if The installed version is 6 or any lower version number.
-
Verify the update endpoint uses HTTP instead of HTTPSUse a network packet analyzer (such as Wireshark) or Windows netmon to capture traffic when Listary performs an update check. Inspect the protocol used for the /check-update endpoint.Affected if The traffic to the update server uses plain HTTP (port 80) rather than HTTPS (port 443).
-
Inspect update configuration filesNavigate to the Listary application data folder (typically %AppData%\Listary or %LocalAppData%\Listary) and examine any configuration files related to updates. Look for URLs or server addresses configured for the update mechanism.Affected if The configuration shows an HTTP URL (starting with http://) for the update or check-update endpoint.
-
Check for cryptographic signature verificationDuring an update attempt, examine the update package download and installation process. Look for any validation steps, logs, or error messages related to signature, hash, or certificate verification of downloaded update files.Affected if No signature, hash, or certificate verification is performed on downloaded update packages before installation.
If the installed Listary version is 6 or lower and the update check uses HTTP (not HTTPS) with no signature verification of update packages, the environment is vulnerable to CVE-2021-41067.
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 HTTPS for all update connections and add cryptographic signature verification of update packages before installation to prevent tampering.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41067 — 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-41067 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