Application ServiceApplication · Synology

CVE-2018-13294

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.Profile in Synology Application Service before 1.5.4-0320 allows remote authenticated users to obtain sensitive system information via the uid 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 · high confidence

Information disclosure vulnerability in the SYNO.Personal.Profile component of Synology Application Service allows authenticated remote attackers to retrieve sensitive system information by manipulating the uid parameter in requests.

MitigationUpgrade Synology Application Service to version 1.5.4-0320 or later to resolve the information exposure. Verify that only authorized users have access to the affected service.

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. Confirm Synology Application Service is installed
    Log into DSM (DiskStation Manager) and open Package Center. Look for 'Synology Application Service' in the installed packages list. Alternatively, check via SSH using 'cat /etc/synoinfo.conf' or listing installed Synology packages.
    Affected if The package is installed and appears in the package list
  2. Verify the installed version number
    In DSM Package Center, click on Synology Application Service and view the version information. Compare the version string (e.g., 1.5.x-xxxx) against 1.5.4-0320. The first three numbers must be less than 1.5.4, or equal to 1.5.4 but with a build number lower than 0320.
    Affected if The version is below 1.5.4-0320 (for example, 1.5.3-0285 or 1.5.4-0315)
  3. Check if SYNO.Personal.Profile API endpoint is accessible
    Send an HTTP GET request to the API endpoint. On a typical Synology NAS, this would be: http://[NAS-IP]:5000/webapi/SYNO.Personal.Profile/1.0/?api=SYNO.Personal.Profile&method=get&version=1. Check if the endpoint responds (with or without authentication).
    Affected if The endpoint returns any response (even an authentication error indicates the component is exposed)
  4. Confirm authentication is required for the profile endpoint
    Attempt an unauthenticated request to the SYNO.Personal.Profile API. If the service returns user profile data or system information without requiring valid credentials, the vulnerability is present. A proper response would be an authentication error.
    Affected if The endpoint returns sensitive information (user profiles, system details) without providing valid authentication credentials

The environment is affected if Synology Application Service is installed with a version lower than 1.5.4-0320 and the SYNO.Personal.Profile API endpoint is accessible and returns information without proper authorization.

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 to resolve the information exposure. Verify that only authorized users have access to the affected service.

Fix this in Application Service Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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