osquery / osquery/osquery

Library libdpkg has vulnerability CVE-2025-6297

Open
#8,765 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

cve libraries security severity-high
Dominant language
C++
Stars
23.6k
Forks
2.6k
Avg merge
6d 7h
Merged PRs (30d)
14

Description

https://nvd.nist.gov/vuln/detail/CVE-2025-6297

It was discovered that dpkg-deb does not properly sanitize directory permissions when extracting a control member into a temporary directory, which is
documented as being a safe operation even on untrusted data. This may result in leaving temporary files behind on cleanup. Given automated and repeated execution of dpkg-deb commands on
adversarial .deb packages or with well compressible files, placed
inside a directory with permissions not allowing removal by a non-root
user, this can end up in a DoS scenario due to causing disk quota
exhaustion or disk full conditions.

NOTE: This is an automated issue created based on the library metadata. Osquery may or may not be affected.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by determining whether osquery invokes dpkg-deb or otherwise uses libdpkg when handling Debian packages, then compare that path with CVE-2025-6297 and the linked NVD details. Done means documenting whether osquery is affected and, if so, identifying the required remediation and a way to verify it.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.