# CVE-2022-27134: EOSIO batdappboomx v327c04cf has an Access-control vulnerability in the `transfer` function of the smart contract which allows remote attack


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-7j9g-fqh9-76xm

## What is CVE-2022-27134?

CVE-2022-27134 is a high-severity vulnerability in n/a, published on 12 May 2022. 

### Official description

EOSIO batdappboomx v327c04cf has an Access-control vulnerability in the `transfer` function of the smart contract which allows remote attackers to win the cryptocurrency without paying ticket fee via the `std::string memo` parameter.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2022-27134?

It affects 1 product.


Products: B1 Eosio Batdappboomx.

## How do I fix CVE-2022-27134?

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

## Is CVE-2022-27134 being exploited?

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

Public exploit code:

- CVE-2022-27134 (github_poc): https://github.com/Kenun99/CVE-batdappboomx

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-27134 and fix it if it is affected.

What it is: CVE-2022-27134 is a high-severity vulnerability in n/a, published on 12 May 2022. 
Exploitation: There is no known exploitation of CVE-2022-27134 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-2022-27134/ (Markdown: https://insights.sbomify.com/CVE-2022-27134/index.md)
```

## Sources

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

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