dbcve.org
Local Run ManagerApplication · Illumina

CVE-2022-1524

MEDIUM · 5.9 CVSS v3.1 Published 2022-06-24
Fix available
A fix is available. Upgrade to after 3.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
LRM version 2.4 and lower does not implement TLS encryption. A malicious actor can MITM attack sensitive data in-transit, including credentials.

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 confidence

LRM version 2.4 and lower lacks TLS encryption for network communications, allowing man-in-the-middle attackers to intercept sensitive data such as credentials as they transit the network.

MitigationEnable TLS encryption for all network communications in LRM, typically through HTTPS/TLS configuration or implementation of secure transport layer protocols.

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
Local Run ManagerApplication
Affected:>= 1.3, <= 3.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed LRM version
    Locate and inspect the Illumina Local Run Manager version information, typically found in the application GUI, About section, or installation metadata files. Use system inventory tools or check LRM application logs for version strings.
    Affected if The installed version is >= 1.3 AND <= 3.1 (2.4 and lower specifically lacks TLS, but versions up to 3.1 are affected)
  2. Verify network protocol configuration
    Examine LRM network communication settings to determine whether HTTP or HTTPS is configured for client-server connections. Check configuration files or administrative interface for transport protocol settings.
    Affected if LRM is configured to use unencrypted HTTP for network communications instead of HTTPS/TLS
  3. Inspect TLS/SSL configuration status
    Review LRM configuration files or settings panel for TLS/SSL encryption options. Determine if TLS encryption is explicitly disabled, not configured, or unavailable in the settings.
    Affected if TLS encryption is disabled, not configured, or the option to enable it is missing from the configuration
  4. Check for TLS certificate deployment
    Examine the LRM installation directory and configuration locations for presence of TLS/SSL certificates or keystore files used for encrypted communications.
    Affected if No TLS certificates are deployed and the application relies on plaintext network communication

A user is affected if their Illumina Local Run Manager version falls between 1.3 and 3.1 AND network communications are configured without TLS encryption (using unencrypted HTTP).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 3.1
Interim mitigation

Enable TLS encryption for all network communications in LRM, typically through HTTPS/TLS configuration or implementation of secure transport layer protocols.

Recommended fix Moderate confidence

Local Run Manager version 3.2 or later

  1. 1. Identify the current Local Run Manager version installed in your environment
  2. 2. Download the latest version of Local Run Manager (version 3.2 or later) from the official vendor source
  3. 3. Create a full backup of the current LRM configuration and any associated data
  4. 4. Stop the Local Run Manager service
  5. 5. Install the upgraded version (3.2 or later) which includes TLS encryption implementation
  6. 6. Verify TLS/SSL is now enabled by checking the LRM configuration settings
  7. 7. Restart the LRM service
  8. 8. Test that all connections to LRM are now encrypted using TLS

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Local Run Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1524 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-1524 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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