CVE-2018-6610 Information disclosure in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2018-6610 and fix it if it is affected.
What it is: CVE-2018-6610 is a high-severity vulnerability in n/a, published on 5 Feb 2018. 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-2018-6610 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-2018-6610/ (Markdown: https://insights.sbomify.com/CVE-2018-6610/index.md)
An attacker can leak user information via a crafted request in the jLike component for Joomla.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2018-6610?
CVE-2018-6610 is a high-severity vulnerability in n/a, published on 5 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Information Leakage exists in the jLike 1.0 component for Joomla! via a task=getUserByCommentId request.
Weakness: CWE-200
Which versions are affected by CVE-2018-6610?
It affects 1 product.
Products include Jlike Project Jlike.
How do I fix CVE-2018-6610?
No fix has been published for CVE-2018-6610 yet. Limit exposure of the affected software until one is available.
Is CVE-2018-6610 being exploited?
There is no known exploitation of CVE-2018-6610 in the wild and no public exploit code.
Public exploit code: 1 Exploit-DB entry.
Sources
Also known as GHSA-7h2p-26cp-f942.