dbcve.org
CalendarApplication · Synology

CVE-2022-22686

HIGH · 8.0 CVSS v3.1 Published 2022-07-26
Fix available
A fix is available. Upgrade to 2.3.4-0631 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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
Cross-Site Request Forgery (CSRF) vulnerability in webapi component in Synology Calendar before 2.3.4-0631 allows remote authenticated users to hijack the authentication of administrators 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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the webapi component of Synology Calendar versions prior to 2.3.4-0631 allows remote authenticated users to hijack administrator authentication through unspecified attack vectors.

MitigationUpgrade Synology Calendar to version 2.3.4-0631 or later to obtain the vendor patch that addresses the CSRF vulnerability.

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
CalendarApplication
Affected:< 2.3.4-0631

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
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Verify Synology Calendar is installed
    Access Synology DSM and open Package Center to confirm Synology Calendar package is installed, or run the command 'pkginfo | grep -i calendar' on the NAS via SSH
    Affected if Synology Calendar package is not found in Package Center or command returns no results (not affected)
  2. Check installed version number
    In Package Center, click on Synology Calendar and view the version information, or run 'cat /var/packages/SynologyCalendar/conf' or check the package info via 'pkginfo -i synocalendar' if available
    Affected if Version displayed is lower than 2.3.4-0631 (for example, 2.3.3-0590 or earlier)
  3. Confirm webapi component is accessible
    Check if the webapi endpoint is exposed by accessing your Synology Calendar URL (typically at /calendar/ or /api/caldav/) via the web browser while logged in as an administrator
    Affected if Web interface is accessible and functional, indicating the webapi component is active
  4. Determine if remote network access is enabled
    Review Synology DSM network settings and Calendar application settings to confirm whether remote access to the calendar interface is permitted from external networks
    Affected if Remote access is enabled and Calendar is accessible from outside the local network, increasing the attack surface for CSRF

A user is affected if Synology Calendar is installed with a version prior to 2.3.4-0631 and the webapi component is accessible to authenticated users, including potentially remote users.

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.3.4-0631 or later
Fixed in 2.3.4-0631
Interim mitigation

Upgrade Synology Calendar to version 2.3.4-0631 or later to obtain the vendor patch that addresses the CSRF vulnerability.

Recommended fix High confidence

Synology Calendar version 2.3.4-0631

  1. 1. Log in to your Synology NAS with administrator privileges
  2. 2. Open Package Center
  3. 3. Locate Synology Calendar in the installed packages list
  4. 4. Click on Synology Calendar and select 'Open'
  5. 5. Navigate to the settings or check for updates within the Calendar package
  6. 6. If an update is available, click 'Update' to install version 2.3.4-0631 or later
  7. 7. Alternatively, manually download the latest Synology Calendar package from the Synology Download Center
  8. 8. In Package Center, click 'Manual Install' and select the downloaded .spk file
Caveat Standard Synology package updates typically preserve settings; minor UI changes may occur

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

Fix this in Calendar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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