# CVE-2018-17213: Auth bypass in n/a

> Unauthenticated attackers can bypass authentication to obtain guest session cookies, enabling further attacks against PrinterOn Central Print Services.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 29 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5g92-4qp2-9882

## What is CVE-2018-17213?

CVE-2018-17213 is a high-severity authentication bypass vulnerability in n/a, published on 29 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in PrinterOn Central Print Services (CPS) through 4.1.4. A user without valid credentials can bypass the authentication process, obtaining a valid session cookie with guest/pseudo-guest level privileges. This cookie can then be further used to perform other attacks.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Printeron Central Print Services.

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

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

## Is CVE-2018-17213 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-17210](https://insights.sbomify.com/CVE-2018-17210/): Auth bypass in n/a (high 8.8)
- [CVE-2018-17211](https://insights.sbomify.com/CVE-2018-17211/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17213 is a high-severity authentication bypass vulnerability in n/a, published on 29 Jul 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-17213 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-2018-17213/ (Markdown: https://insights.sbomify.com/CVE-2018-17213/index.md)
```

## Sources

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

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