Monitoring
Approved changes feed: RSS · Atom
cpe:2.3:a:ctfer:monitoring:*:*:*:*:*:go:*:*
part: a version: * update: *
| Vendor | Ctfer (d4c74111-33f7-5de8-9d61-afc37e79c2bb) |
|---|---|
| Product | Monitoring (5ccc8a75-97f6-5616-a607-452283a449d7) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | go |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-32771 |
vulnerable | 2026-06-08 07:57:18.145781 |
Monitoring is vulnerable to Archive Slip due to missing checks in sanitization
The CTFer.io Monitoring component is in charge of the collection, process and storage of various signals (i.e. logs, metrics and distributed traces). In versions prior to 0.2.2, the sanitizeArchivePath function in pkg/extract/extract.go (lines 248–254) is vulnerable to Path Traversal due to a missing trailing path separator in the strings.HasPrefix check. The extractor allows arbitrary file writes (e.g., overwriting shell configs, SSH keys, kubeconfig, or crontabs), enabling RCE and persistent backdoors. The attack surface is further amplified by the default ReadWriteMany PVC access mode, which lets any pod in the cluster inject a malicious payload. This issue has been fixed in version 0.2.2.
Published: 2026-03-20T00:29:23.804Z
Updated: 2026-03-20T16:45:32.747Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.