CVE-2013-4868 Information disclosure in n/a
Medium 5.3
Published
Updated
Check this codebase for CVE-2013-4868 and fix it if it is affected.
What it is: CVE-2013-4868 is a medium-severity vulnerability in n/a, published on 27 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-4868 exists.
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-2013-4868/ (Markdown: https://insights.sbomify.com/CVE-2013-4868/index.md)
The Karotz API exposes session tokens, allowing attackers to potentially hijack user sessions and access private data.
- 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-2013-4868?
CVE-2013-4868 is a medium-severity vulnerability in n/a, published on 27 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Karotz API 12.07.19.00: Session Token Information Disclosure
Weakness: CWE-200
Which versions are affected by CVE-2013-4868?
It affects 1 product.
Products include Karotz Api.
How do I fix CVE-2013-4868?
No fix has been published for CVE-2013-4868 yet. Limit exposure of the affected software until one is available.
Is CVE-2013-4868 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-4868 exists.
Public exploit code: 1 Exploit-DB entry.
Sources
Also known as GHSA-h5fw-xv87-xfpg.