Application ServiceApplication · Synology

CVE-2018-13295

MEDIUM · 6.5 CVSS v3.0 Published 2019-04-01
Fix available
A fix is available. Upgrade to 1.5.4-0320 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Information exposure vulnerability in SYNO.Personal.Application.Info in Synology Application Service before 1.5.4-0320 allows remote authenticated users to obtain sensitive system information via the version parameter.

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

Information exposure vulnerability in Synology Application Service allows remote authenticated users to obtain sensitive system information via the version parameter in the SYNO.Personal.Application.Info API endpoint. The flaw enables privilege escalation through information disclosure, potentially revealing configuration details, paths, or system specifics that should not be accessible to standard users.

MitigationUpgrade Synology Application Service to version 1.5.4-0320 or later. If immediate patching is not possible, restrict API access to only trusted users and monitor for anomalous queries to the affected endpoint.

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
Application ServiceApplication
Affected:< 1.5.4-0320

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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/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 if Synology Application Service is installed
    On the Synology NAS, check the installed packages via Package Center or run 'dpkg -l | grep -i synology' or 'cat /var/packages/MyDS/package.info' to list installed Synology packages.
    Affected if Synology Application Service or related Synology package is present on the system.
  2. Determine the version of Synology Application Service
    Check the package version by inspecting the package info file at /var/packages/MyDS/package.info or via the Synology Package Center interface. Look for the version field.
    Affected if The installed version is lower than 1.5.4-0320 (e.g., 1.5.3-xxxx or earlier).
  3. Verify the SYNO.Personal.Application.Info API endpoint exists and is accessible
    If you have CLI access, search for API configuration files containing 'Personal.Application.Info' in the Synology web directory (typically under /var/packages/MyDS/ui/). Check if the API is enabled in the package configuration.
    Affected if The SYNO.Personal.Application.Info endpoint is present and exposed in the API configuration.
  4. Check for suspicious API queries in logs
    Review Synology logs (via Log Center or /var/log/messages) for access patterns to the SYNO.Personal.Application.Info endpoint. Look for repeated queries from standard user accounts that may indicate probing.
    Affected if Unusual or repeated queries to this endpoint are observed, especially from non-admin accounts.

A user is affected if Synology Application Service is installed with a version lower than 1.5.4-0320 and the SYNO.Personal.Application.Info API endpoint 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.

From vendor data
Upgrade available Upgrade to 1.5.4-0320 or later
Fixed in 1.5.4-0320
Interim mitigation

Upgrade Synology Application Service to version 1.5.4-0320 or later. If immediate patching is not possible, restrict API access to only trusted users and monitor for anomalous queries to the affected endpoint.

Fix this in Application Service Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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