# CVE-2023-29218: Business logic in n/a

> Attackers can reduce a target account's reputation score by coordinating negative signals, though the vendor considers this intended behavior.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2023
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-rfh2-62gc-x7hw

## What is CVE-2023-29218?

CVE-2023-29218 is a high-severity vulnerability in n/a, published on 3 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Twitter Recommendation Algorithm through ec83d01 allows attackers to cause a denial of service (reduction of reputation score) by arranging for multiple Twitter accounts to coordinate negative signals regarding a target account, such as unfollowing, muting, blocking, and reporting, as exploited in the wild in March and April 2023. NOTE: Vendor states that allowing users to unfollow, mute, block, and report tweets and accounts and the impact of these negative engagements on Twitter’s ranking algorithm is a conscious design decision, rather than a security vulnerability.

## Which versions are affected by CVE-2023-29218?

It affects 1 product.


Products: Twitter Recommendation Algorithm.

## How do I fix CVE-2023-29218?

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

## Is CVE-2023-29218 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29218 and fix it if it is affected.

What it is: CVE-2023-29218 is a high-severity vulnerability in n/a, published on 3 Apr 2023. 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-2023-29218 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-2023-29218/ (Markdown: https://insights.sbomify.com/CVE-2023-29218/index.md)
```

## Sources

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

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