{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-29489 exists.","fix":"No fix has been published for CVE-2025-29489 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-29489 is a medium-severity vulnerability in Libming Libming, published on 27 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-29489 and fix it if it is affected.\n\nWhat it is: CVE-2025-29489 is a medium-severity vulnerability in Libming Libming, published on 27 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-29489 exists.\n\nAffected product: Libming Libming. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-29489/ (Markdown: https://insights.sbomify.com/CVE-2025-29489/index.md)","id":"CVE-2025-29489","markdown":"https://insights.sbomify.com/CVE-2025-29489/index.md","name":"CVE-2025-29489","record":{"aliases":["GHSA-hqf3-3h38-frmh","UBUNTU-CVE-2025-29489"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"libming SWF library","requires_auth":"none","summary":"A memory leak in libming allows attackers to potentially disclose sensitive information via crafted SWF files.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libming","vendor":"libming"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"libming v0.4.8 was discovered to contain a memory leak via the parseSWF_MORPHLINESTYLES function.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2025-29489","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"libming:libming","products":["libming:libming"],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2025-29490"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2025-29488"},"products":["n/a"],"published":"2025-03-27","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-50628","kev_date_added":null,"published":"2023-12-20"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2020-11894","kev_date_added":null,"published":"2020-04-19"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2020-11895","kev_date_added":null,"published":"2020-04-19"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2019-16705","kev_date_added":null,"published":"2019-09-23"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2023-36239","kev_date_added":null,"published":"2023-06-22"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2023-31976","kev_date_added":null,"published":"2023-05-09"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2020-6628","kev_date_added":null,"published":"2020-01-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-28","vendors":["n/a"]},"summary":"A memory leak in libming allows attackers to potentially disclose sensitive information via crafted SWF files.","url":"https://insights.sbomify.com/CVE-2025-29489/"}