# CVE-2018-13295: Information disclosure in Application Service

> Remote authenticated users can obtain sensitive system information via the version parameter in Synology Application Service.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r8m8-266c-22qg

## What is CVE-2018-13295?

CVE-2018-13295 is a medium-severity vulnerability in Synology Application Service, published on 1 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-13295?

It affects 1 product.


Products: Synology Application Service.

## How do I fix CVE-2018-13295?

No fix has been published for CVE-2018-13295 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-13295 being exploited?

There is no known exploitation of CVE-2018-13295 in the wild and no public exploit code.

## Other vulnerabilities in Synology Application Service

- [CVE-2018-13294](https://insights.sbomify.com/CVE-2018-13294/): Information disclosure in Application Service (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-13295 and fix it if it is affected.

What it is: CVE-2018-13295 is a medium-severity vulnerability in Synology Application Service, published on 1 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-13295 in the wild and no public exploit code.

Affected product: Synology Application Service. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-13295/ (Markdown: https://insights.sbomify.com/CVE-2018-13295/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-13295
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-13295
- OSV: https://osv.dev/vulnerability/CVE-2018-13295

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-13295/
Summaries are generated and may contain mistakes; the official description above is the record.