Carddav ServerApplication · Synology

CVE-2022-27613

HIGH · 8.8 CVSS v3.1 Published 2022-07-28
Fix available
A fix is available. Upgrade to 6.0.10-0153 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Improper neutralization of special elements used in an SQL command ('SQL Injection') vulnerability in webapi component in Synology CardDAV Server before 6.0.10-0153 allows remote authenticated users to inject SQL commands 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

SQL injection vulnerability in Synology CardDAV Server's webapi component allows remote authenticated attackers to inject arbitrary SQL commands. The vulnerability affects versions prior to 6.0.10-0153 and is exploitable via unspecified vectors in the webapi.

MitigationUpdate to Synology CardDAV Server version 6.0.10-0153 or later. As a secondary measure, review and restrict CardDAV Server access to only necessary authenticated users until the patch can be applied.

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
Carddav ServerApplication
Affected:< 6.0.10-0153

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Identify if Synology CardDAV Server is installed
    Check your Synology NAS for the CardDAV Server package. This can be done via Package Center in the Synology DSM interface, or by searching for CardDAV-related processes or installed packages on the NAS filesystem.
    Affected if CardDAV Server package is installed on the system
  2. Determine the installed CardDAV Server version
    Access the Synology DSM interface, open Package Center, locate the CardDAV Server package, and view its version information. Alternatively, use the command line to query the installed package version if available.
    Affected if The installed version is lower than 6.0.10-0153
  3. Verify the webapi component is accessible
    Check if the CardDAV Server webapi endpoint is exposed and accessible. This typically involves verifying network accessibility of the CardDAV Server web interface or API endpoints.
    Affected if The webapi component is exposed and accessible over the network

Your environment is affected if Synology CardDAV Server is installed with a version lower than 6.0.10-0153 and the webapi component is accessible to authenticated 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 6.0.10-0153 or later
Fixed in 6.0.10-0153
Interim mitigation

Update to Synology CardDAV Server version 6.0.10-0153 or later. As a secondary measure, review and restrict CardDAV Server access to only necessary authenticated users until the patch can be applied.

Recommended fix High confidence

CardDAV Server version 6.0.10-0153 or later

  1. Log into your Synology NAS using your admin credentials
  2. Open the Synology DiskStation Manager (DSM) interface
  3. Navigate to Package Center
  4. Locate CardDAV Server in the list of installed packages
  5. Click on CardDAV Server and select 'Update' to install the latest available version
  6. Verify that the installed version is 6.0.10-0153 or later
  7. After updating, ensure that CardDAV Server is functioning normally

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

Fix this in Carddav Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,100
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,360.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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