CVE-2022-3090
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 · uneditedRed Lion Controls Crimson 3.0 versions 707.000 and prior, Crimson 3.1 versions 3126.001 and prior, and Crimson 3.2 versions 3.2.0044.0 and prior are vulnerable to path traversal. When attempting to open a file using a specific path, the user's password hash is sent to an arbitrary host. This could allow an attacker to obtain user credential hashes.
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 confidenceRed Lion Controls Crimson software versions prior to 3.2.0044.0 contain a path traversal vulnerability where opening a file via a specific path causes the user's password hash to be transmitted to an arbitrary host specified by an attacker, enabling credential theft.
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< 3.0= 3.0= 3.1= 3.2CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify installed Crimson versionCheck the software version through the Windows Add/Remove Programs list, or launch Crimson and look for the version information in the Help > About dialog, or check the executable's file propertiesAffected if The version is < 3.0, = 3.0, = 3.1, or = 3.2 (any version prior to 3.2.0044.0)
-
Confirm the specific minor build numberLocate the exact four-digit build suffix in the version string (for example, in version 3.2.0xxx), as the fix is version 3.2.0044.0 or laterAffected if The build number is below 0044 (for the 3.2 branch), or if on 3.0 or 3.1 branches, any version without the equivalent patch
-
Inspect outbound network connectionsUse network monitoring tools (Windows Firewall logging, Wireshark, or netstat -abn) to observe if Crimson is making unexpected outbound connections to unknown hostsAffected if The software initiates outbound network traffic to hosts you did not configure or expect, which could indicate credential exfiltration
-
Review system logs for anomaliesCheck Windows Event Viewer for unusual process execution events or network connection attempts around the time Crimson was openedAffected if There are logs showing unexpected network behavior or suspicious process activity originating from Crimson
You are affected if the installed Crimson version is any release prior to 3.2.0044.0, or any 3.0.x or 3.1.x release without the equivalent patch applied.
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 data3.0
Update Crimson to the latest patched version (3.2.0044.1 or later, or equivalent fixes for 3.0/3.1 branches). Additionally, implement network segmentation and outbound firewall rules to prevent the application from making unauthorized connections to arbitrary hosts.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3090 — 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-3090 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