CVE-2013-4947 Other in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2013-4947 and fix it if it is affected.
What it is: CVE-2013-4947 is a high-severity vulnerability in n/a, published on 29 Jul 2013. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2013-4947 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-4947/ (Markdown: https://insights.sbomify.com/CVE-2013-4947/index.md)
Unspecified vulnerability in Sawmill's update and build database page allows remote attackers to cause unknown impact.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Over the internet
- Victim action needed
- Not stated
- Fix
- None listed
What is CVE-2013-4947?
CVE-2013-4947 is a high-severity vulnerability in n/a, published on 29 Jul 2013. It can be exploited over the network.
Official description
Unspecified vulnerability in the update and build database page in Sawmill before 8.6.3 allows remote attackers to have unknown impact and attack vectors.
Which versions are affected by CVE-2013-4947?
It affects 1 product.
Products include Sawmill Sawmill.
How do I fix CVE-2013-4947?
No fix has been published for CVE-2013-4947 yet. Limit exposure of the affected software until one is available.
Is CVE-2013-4947 being exploited?
There is no known exploitation of CVE-2013-4947 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2017-5496 Information disclosure in n/a
- CVE-2005-1900 Auth bypass in n/a
- CVE-2000-0589 Weak cryptography in n/a
- CVE-2000-0588 SawMill 5.0.21 CGI program allows remote attackers to read the first line of arbitrary files by listing the file in the rfcf parameter, whos
- CVE-2002-0265 Privilege escalation in n/a
Sources
Also known as GHSA-m9h4-p64h-2qfh.