# CVE-2021-43974: Missing authorization in n/a

> Attackers can bypass server-side restrictions to create unauthorized accounts in SysAid ITIL by directly accessing the registration endpoint.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4p5h-hrqx-rj2r

## What is CVE-2021-43974?

CVE-2021-43974 is a medium-severity missing authorization vulnerability in n/a, published on 11 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in SysAid ITIL 20.4.74 b10. The /enduserreg endpoint is used to register end users anonymously, but does not respect the server-side setting that determines if anonymous users are allowed to register new accounts. Configuring the server-side setting to disable anonymous user registration only hides the client-side registration form. An attacker can still post registration data to create new accounts without prior authentication.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2021-43974?

It affects 1 product.


Products: Sysaid Itil.

## How do I fix CVE-2021-43974?

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

## Is CVE-2021-43974 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43974 and fix it if it is affected.

What it is: CVE-2021-43974 is a medium-severity missing authorization vulnerability in n/a, published on 11 Jan 2022. 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-2021-43974 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-2021-43974/ (Markdown: https://insights.sbomify.com/CVE-2021-43974/index.md)
```

## Sources

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

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