# CVE-2017-16673: Auth bypass in n/a

> An attacker can impersonate a backup appliance to pair with the agent and issue requests, leading to unauthorized access and potential data exposure.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-69r5-6x57-4ffx

## What is CVE-2017-16673?

CVE-2017-16673 is a medium-severity authentication bypass vulnerability in n/a, published on 9 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Datto Backup Agent 1.0.6.0 and earlier does not authenticate incoming connections. This allows an attacker to impersonate a Datto Backup Appliance to "pair" with the agent and issue requests to this agent, if the attacker can reach the agent on TCP port 25566 or 25568, and send unspecified "specific information" by which the agent identifies a network device that is "appearing to be a valid Datto."

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

## Which versions are affected by CVE-2017-16673?

It affects 1 product.


Products: Datto Backup Agent.

## How do I fix CVE-2017-16673?

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

## Is CVE-2017-16673 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16673 and fix it if it is affected.

What it is: CVE-2017-16673 is a medium-severity authentication bypass vulnerability in n/a, published on 9 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-16673 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-2017-16673/ (Markdown: https://insights.sbomify.com/CVE-2017-16673/index.md)
```

## Sources

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

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