CVE-2013-3925 Atlassian Crowd 2.5.x before 2.5.4, 2.6.x before 2.6.3, 2.3.8, and 2.4.9 allows remote attackers to read arbitrary files and send HTTP reque
Medium 5.8
Published
Updated
Check this codebase for CVE-2013-3925 and fix it if it is affected.
What it is: CVE-2013-3925 is a medium-severity vulnerability in n/a, published on 1 Jul 2013.
Exploitation: There is no known exploitation of CVE-2013-3925 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-2013-3925/ (Markdown: https://insights.sbomify.com/CVE-2013-3925/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2013-3925?
CVE-2013-3925 is a medium-severity vulnerability in n/a, published on 1 Jul 2013.
Official description
Atlassian Crowd 2.5.x before 2.5.4, 2.6.x before 2.6.3, 2.3.8, and 2.4.9 allows remote attackers to read arbitrary files and send HTTP requests to intranet servers via a request to (1) /services/2 or (2) services/latest with a DTD containing an XML external entity declaration in conjunction with an entity reference.
Weakness: CWE-20
Which versions are affected by CVE-2013-3925?
It affects 1 product.
Products include Atlassian Crowd.
How do I fix CVE-2013-3925?
No fix has been published for CVE-2013-3925 yet. Limit exposure of the affected software until one is available.
Is CVE-2013-3925 being exploited?
There is no known exploitation of CVE-2013-3925 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-w3j4-57m3-994j.