# CVE-2021-33981: Information disclosure in n/a

> An authenticated attacker can access other users' personal information and license images via insecure direct object references in the iOS app.

- **Severity:** Medium 4.3 (`CVSS:3.1/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:** 8 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hhpx-68fp-4gm4

## What is CVE-2021-33981?

CVE-2021-33981 is a medium-severity vulnerability in n/a, published on 8 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An insecure, direct object vulnerability in hunting/fishing license retrieval function of the "Fish | Hunt FL" iOS app versions 3.8.0 and earlier allows a remote authenticated attacker to retrieve other people's personal information and images of their hunting/fishing licenses.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Myfwc Fish \| Hunt Fl.

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

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

## Is CVE-2021-33981 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-33982](https://insights.sbomify.com/CVE-2021-33982/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-33981 is a medium-severity vulnerability in n/a, published on 8 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-33981 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-33981/ (Markdown: https://insights.sbomify.com/CVE-2021-33981/index.md)
```

## Sources

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

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