Note StationApplication · Synology

CVE-2022-27619

MEDIUM · 5.9 CVSS v3.1 Published 2022-08-03
Fix available
A fix is available. Upgrade to 2.2.2-609 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
Cleartext transmission of sensitive information vulnerability in authentication management in Synology Note Station Client before 2.2.2-609 allows man-in-the-middle attackers to obtain sensitive information via unspecified vectors.

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

Synology Note Station Client before version 2.2.2-609 transmits authentication credentials and potentially other sensitive information in cleartext (unencrypted) format. A man-in-the-middle attacker on the network path between client and server can intercept these credentials by capturing network traffic.

MitigationUpgrade Synology Note Station Client to version 2.2.2-609 or later. Until upgraded, avoid using the client over untrusted networks (e.g., public WiFi) where MITM attacks are feasible.

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
Note StationApplication
Affected:< 2.2.2-609

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 Synology Note Station Client version
    On Windows, open Control Panel > Programs and Features and locate Synology Note Station in the list to view the installed version. On macOS, navigate to the application in Finder, right-click and select Get Info to view the version. On mobile (iOS/Android), go to the app store or device settings > Apps > Note Station to see the version number.
    Affected if The installed version is lower than 2.2.2-609
  2. Compare version against affected range
    Take the version number you identified and compare it numerically to 2.2.2-609. Note that versions like 2.2.2-600, 2.2.1, or any build before 609 are all in the affected range.
    Affected if The client version is less than 2.2.2-609 (for example, 2.2.2-500 or 2.2.1-123)
  3. Assess network exposure risk
    Determine whether the client connects to the Synology server over networks where a man-in-the-middle attack is possible, such as public WiFi hotspots, untrusted corporate networks, or shared network environments.
    Affected if The vulnerable client version connects to the server over any untrusted or public network where an attacker could intercept network traffic

A user is affected if the Synology Note Station Client version is below 2.2.2-609 AND the client communicates with the server over a network where MITM interception is feasible.

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 2.2.2-609 or later
Fixed in 2.2.2-609
Interim mitigation

Upgrade Synology Note Station Client to version 2.2.2-609 or later. Until upgraded, avoid using the client over untrusted networks (e.g., public WiFi) where MITM attacks are feasible.

Recommended fix Moderate confidence

2.2.2-609 or later

  1. 1. Open Synology Note Station Client on your system
  2. 2. Navigate to Help > About to verify the current version number
  3. 3. Uninstall the current version of Synology Note Station Client
  4. 4. Download Note Station Client version 2.2.2-609 or later from the official Synology download center at www.synology.com
  5. 5. Install the updated Note Station Client version

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

Fix this in Note Station Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27619 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-27619 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