CVE-2019-1020010 Misskey before 10.102.4 allows hijacking a user's token.
Medium 6.1
Published
Updated
Check this codebase for CVE-2019-1020010 and fix it if it is affected.
What it is: CVE-2019-1020010 is a medium-severity vulnerability in Misskey, published on 29 Jul 2019.
Exploitation: There is no known exploitation of CVE-2019-1020010 in the wild and no public exploit code.
Affected product: Misskey. 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-2019-1020010/ (Markdown: https://insights.sbomify.com/CVE-2019-1020010/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2019-1020010?
CVE-2019-1020010 is a medium-severity vulnerability in Misskey, published on 29 Jul 2019.
Official description
Misskey before 10.102.4 allows hijacking a user's token.
Weakness: CWE-79
Which versions are affected by CVE-2019-1020010?
It affects 1 product.
Products include Misskey Misskey.
How do I fix CVE-2019-1020010?
No fix has been published for CVE-2019-1020010 yet. Limit exposure of the affected software until one is available.
Is CVE-2019-1020010 being exploited?
There is no known exploitation of CVE-2019-1020010 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Other vulnerabilities in Misskey
- CVE-2025-25306 Misskey's Incomplete Patch of CVE-2024-52591 Leads to Forgery of Federated Notes
- CVE-2023-49079 Misskey's missing signature validation allows arbitrary users to impersonate any remote user.
- CVE-2026-28431 Misskey lacks proper authorization checks and input validation
- CVE-2023-52139 Misskey vulnerable to improper authorization when accessing with third-party application
- CVE-2024-52590 Missing validation allows spoofed profiles in Misskey
Sources
Also known as GHSA-373r-4p5w-qjr7, GHSA-6qw9-6jxq-xj3p.