# OSV-2025-275: UNKNOWN READ in void std::__1::vector>::__cons > An unknown read vulnerability in the Poco library's NTLM credential parsing can cause a crash, potentially leading to denial of service. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not stated - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 14 Apr 2025 ## What is OSV-2025-275? OSV-2025-275 is a memory corruption vulnerability in poco, published on 14 Apr 2025. It can be exploited over the network, with no action from the victim. ### Official description OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=410115359 ``` Crash type: UNKNOWN READ Crash state: void std::__1::vector>::__cons Poco::Net::NTLMCredentials::parseChallengeMessage Poco::Net::HTTPNTLMCredentials::createNTLMMessage ``` ## Which versions are affected by OSV-2025-275? 1 open source package ship an affected version, including poco. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `poco` | OSS-Fuzz | All versions | None | ## How do I fix OSV-2025-275? No fix has been published for OSV-2025-275 yet. Limit exposure of the affected software until one is available. ## Is OSV-2025-275 being exploited? There is no known exploitation of OSV-2025-275 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for OSV-2025-275 and fix it if it is affected. What it is: OSV-2025-275 is a memory corruption vulnerability in poco, published on 14 Apr 2025. It can be exploited over the network, with no action from the victim. Exploitation: There is no known exploitation of OSV-2025-275 in the wild and no public exploit code. Affected packages and fixed versions: - poco (OSS-Fuzz): affected all versions; no fix listed 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/OSV-2025-275/ (Markdown: https://insights.sbomify.com/OSV-2025-275/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/OSV-2025-275 --- From sbomify Insights: https://insights.sbomify.com/OSV-2025-275/ Summaries are generated and may contain mistakes; the official description above is the record.