CVE-2022-44574
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 improper authentication vulnerability exists in Avalanche version 6.3.x and below allows unauthenticated attacker to modify properties on specific port.
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 confidenceImproper authentication vulnerability in Avalanche <= 6.3.x allows unauthenticated attackers to modify properties on a specific port, bypassing intended authentication controls.
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< 6.4.0CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Check Ivanti Avalanche installed versionLocate the Avalanche installation directory and find the version information, typically in an 'about' page within the Avalanche console, a version file, or check the installer metadata. Common locations include the admin web interface or a version.txt file in the installation folder.Affected if The installed version is any release prior to 6.4.0 (versions 6.3.x and earlier).
-
Identify Avalanche listening portsReview Avalanche server configuration or running services to determine which network ports the application is listening on. Check the server's configuration files, service settings, or use netstat/port scanning tools to list active ports.Affected if The vulnerable port (the specific port that accepts property modifications) is open and listening on the server.
-
Verify port exposure to networkDetermine if the vulnerable port is accessible from network locations other than localhost. Check firewall rules, network binding settings, and whether the port is bound to 0.0.0.0 versus localhost only.Affected if The vulnerable port is accessible from remote network locations (not restricted to localhost or trusted internal networks).
-
Test authentication on the vulnerable portIf accessible, send a legitimate property modification request to the specific port without providing authentication credentials and observe the server response.Affected if The server accepts and processes unauthenticated requests to modify properties on that port.
You are affected if Avalanche version is below 6.4.0 AND the specific vulnerable port is exposed to the network where unauthenticated attackers could reach it.
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.
dbcve · scoped6.4.0
Upgrade to a version beyond 6.3.x that includes the authentication fix, and apply network segmentation or firewall rules to restrict access to the vulnerable port until patched.
Avalanche 6.4.0
- Obtain Avalanche version 6.4.0 or later from the official Ivanti download portal or support channels
- Follow standard Ivanti Avalanche upgrade documentation for your deployment type
- Verify the upgrade was successful by checking the Avalanche version in the administration console
- Confirm the specific port referenced in the vulnerability is no longer accessible without authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44574 — 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-2022-44574 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