{"answers":{"affected":"1 open source package ship an affected version, including qt.","exploited":"There is no known exploitation of OSV-2022-327 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2022-327 yet. Limit exposure of the affected software until one is available.","what":"OSV-2022-327 is an use after free vulnerability in qt, published on 10 Apr 2022."},"fix_prompt":"Check this codebase for OSV-2022-327 and fix it if it is affected.\n\nWhat it is: OSV-2022-327 is an use after free vulnerability in qt, published on 10 Apr 2022. \nExploitation: There is no known exploitation of OSV-2022-327 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- qt (OSS-Fuzz): affected all versions; no fix listed\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/OSV-2022-327/ (Markdown: https://insights.sbomify.com/OSV-2022-327/index.md)","id":"OSV-2022-327","markdown":"https://insights.sbomify.com/OSV-2022-327/index.md","name":"OSV-2022-327","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Qt Core library","requires_auth":"none","summary":"A stack-use-after-return vulnerability in Qt's QSemaphore allows attackers to potentially execute arbitrary code or cause a denial of service via crafted input.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46525\n\nThe issue already existed before oss-fuzz could reproduce it. oss-fuzz found\nit after qdrawhelper routines were made multithreaded. There might be ways to\ntrigger the issue before that.\n\n```\nCrash type: Stack-use-after-return WRITE 8\nCrash state:\nQSemaphore::release\nstd::__1::__function::__func\u003cvoid handleSpans\u003cBlendSrcGeneric\u003e\nFunctionRunnable::run\n```","ecosystems":["OSS-Fuzz"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Stack-use-after-return in QSemaphore::release","id":"OSV-2022-327","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"OSS-Fuzz","product":null,"products":[],"type":"use_after_free","year":"2022"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"OSS-Fuzz","fixed":[],"introduced":[],"last_affected":[],"package":"qt","purl":"pkg:generic/qt","source":"OSV-2022-327"}],"products":null,"published":"2022-04-10","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"OSS-Fuzz","prefix":"OSV"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A stack-use-after-return vulnerability in Qt's QSemaphore allows attackers to potentially execute arbitrary code or cause a denial of service via crafted input.","url":"https://insights.sbomify.com/OSV-2022-327/"}