# CVE-2015-2081: Code injection in n/a

> Unauthenticated attackers can execute arbitrary code on Datto ALTO and SIRIS devices via vulnerable PHP scripts.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fg6j-jrpq-q63g

## What is CVE-2015-2081?

CVE-2015-2081 is a critical code injection vulnerability in n/a, published on 20 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Datto ALTO and SIRIS devices allow Remote Code Execution via unauthenticated requests to PHP scripts.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2015-2081?

It affects 8 products.


Products: Datto Alto 2 Firmware, Datto Alto 3 Firmware, Datto Alto Imaged Firmware, Datto Alto Xl Firmware, Datto Siris 2 Firmware, Datto Siris 3 Firmware, Datto Siris 3 X All-Flash Firmware, Datto Siris Virtual Firmware.

## How do I fix CVE-2015-2081?

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

## Is CVE-2015-2081 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-9254](https://insights.sbomify.com/CVE-2015-9254/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2015-9255](https://insights.sbomify.com/CVE-2015-9255/): Information disclosure in n/a (medium 5.3)
- [CVE-2015-9256](https://insights.sbomify.com/CVE-2015-9256/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2081 and fix it if it is affected.

What it is: CVE-2015-2081 is a critical code injection vulnerability in n/a, published on 20 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-2081 in the wild and no public exploit code.

Affected product: n/a. 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-2015-2081/ (Markdown: https://insights.sbomify.com/CVE-2015-2081/index.md)
```

## Sources

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

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