Skip to content
This page tracks the Debian fix status. The vulnerability itself is described on the main CVE page. View CVE-2022-3276 →
Unrated

Vulnerability in puppet-module-puppetlabs-mysql

DEBIAN-CVE-2022-3276 First seen on SecPulse

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as DEBIAN-CVE-2022-3276 has been found in puppet-module-puppetlabs-mysql.
Successful exploitation can lead to full system takeover.
What to do: upgrade puppet-module-puppetlabs-mysql to 15.0.0-1 or later.
If unsure, ask your IT team or search "puppet-module-puppetlabs-mysql DEBIAN-CVE-2022-3276" on the vendor's site.

DEBIAN-CVE-2022-3276 (puppet-module-puppetlabs-mysql)
Attack vector: remote (network-reachable) / no user interaction
Patched: 15.0.0-1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

What is the problem

A vulnerability (unclassified) exists in puppet-module-puppetlabs-mysql.

Affected scope

Check the vendor advisory for the affected versions of puppet-module-puppetlabs-mysql.

Severity

Severity: ?. Successful exploitation can lead to full system takeover.

How to fix

Update to 15.0.0-1.

Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'puppet-module-puppetlabs-mysql' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposureidentify
    grep -r 'puppet-module-puppetlabs-mysql' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で puppet-module-puppetlabs-mysql を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patchpatch
    Upgrade puppet-module-puppetlabs-mysql to 15.0.0-1

    ステージング環境で 15.0.0-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verificationverify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

EcosystemPackageAffectedFixed
Debian:11 puppet-module-puppetlabs-mysql
All versions
—
Debian:12 puppet-module-puppetlabs-mysql
All versions
—
Debian:13 puppet-module-puppetlabs-mysql
< 15.0.0-1
15.0.0-1
Debian:14 puppet-module-puppetlabs-mysql
< 15.0.0-1
15.0.0-1
Original description The description as published by the source.

Command injection is possible in the puppetlabs-mysql module prior to version 13.0.0. A malicious actor is able to exploit this vulnerability only if they are able to provide unsanitized input to the module. This condition is rare in most deployments of Puppet and Puppet Enterprise.

Source: OSV.dev (Open Source Vulnerabilities) OSV

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details