CVE-2013-0274 upnp.c in libpurple in Pidgin before 2.10.7 does not properly terminate long strings in UPnP responses, which allows remote attackers to cau
Low 2.9
Published
Updated
Check this codebase for CVE-2013-0274 and fix it if it is affected.
What it is: CVE-2013-0274 is a low-severity vulnerability in Pidgin Pidgin, published on 16 Feb 2013.
Exploitation: There is no known exploitation of CVE-2013-0274 in the wild and no public exploit code.
Affected product: Pidgin Pidgin. 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-0274/ (Markdown: https://insights.sbomify.com/CVE-2013-0274/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2013-0274?
CVE-2013-0274 is a low-severity vulnerability in Pidgin Pidgin, published on 16 Feb 2013.
Official description
upnp.c in libpurple in Pidgin before 2.10.7 does not properly terminate long strings in UPnP responses, which allows remote attackers to cause a denial of service (application crash) by leveraging access to the local network.
Which versions are affected by CVE-2013-0274?
It affects 1 product.
Products include Pidgin Pidgin.
How do I fix CVE-2013-0274?
Upgrade to a fixed version.
Is CVE-2013-0274 being exploited?
There is no known exploitation of CVE-2013-0274 in the wild and no public exploit code.
Other vulnerabilities in Pidgin Pidgin
Sources
Also known as DEBIAN-CVE-2013-0274, GHSA-63v2-6jjq-v396.