CVE-2010-1620 Integer overflow in the load_iface function in Tools/gdomap.c in gdomap in GNUstep Base before 1.20.0 might allow context-dependent attacker
High 7.2
Published
Updated
Check this codebase for CVE-2010-1620 and fix it if it is affected.
What it is: CVE-2010-1620 is a high-severity vulnerability in n/a, published on 12 May 2010.
Exploitation: There is no known exploitation of CVE-2010-1620 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-2010-1620/ (Markdown: https://insights.sbomify.com/CVE-2010-1620/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2010-1620?
CVE-2010-1620 is a high-severity vulnerability in n/a, published on 12 May 2010.
Official description
Integer overflow in the load_iface function in Tools/gdomap.c in gdomap in GNUstep Base before 1.20.0 might allow context-dependent attackers to execute arbitrary code via a (1) file or (2) socket that provides configuration data with many entries, leading to a heap-based buffer overflow.
Weakness: CWE-189
Which versions are affected by CVE-2010-1620?
It affects 1 product.
Products include Gnustep Gnustep Base.
How do I fix CVE-2010-1620?
Upgrade to a fixed version.
Is CVE-2010-1620 being exploited?
There is no known exploitation of CVE-2010-1620 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as DEBIAN-CVE-2010-1620, GHSA-3qjp-mpc4-r9xg.