Vulnerability in puppet-module-puppetlabs-apache (DEBIAN-CVE-2017-2299)

Summary

Vulnerability in puppet-module-puppetlabs-apache (DEBIAN-CVE-2017-2299). Confidential information can be exposed externally. Exploitable via ssl_ca. Mitigation: upgrade to 3.0.0-1 or later.

Original description

The description as published by the source.

Versions of the puppetlabs-apache module prior to 1.11.1 and 2.1.0 make it very easy to accidentally misconfigure TLS trust. If you specify the ssl_ca parameter but do not specify the ssl_certs_dir parameter, a default will be provided for the ssl_certs_dir that will trust certificates from any of the system-trusted certificate authorities. This did not affect FreeBSD.

Source: OSV.dev (Open Source Vulnerabilities) OSV

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-2017-2299 has been found in puppet-module-puppetlabs-apache.
Attackers can target a specific entry point like ssl_ca over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade puppet-module-puppetlabs-apache to 3.0.0-1 or later.
If unsure, ask your IT team or search "puppet-module-puppetlabs-apache DEBIAN-CVE-2017-2299" on the vendor's site.

DEBIAN-CVE-2017-2299 (puppet-module-puppetlabs-apache)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: ssl_ca / ssl_certs_dir
Patched: 3.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-apache. Attackers reach the vulnerable code path via ssl_ca without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of puppet-module-puppetlabs-apache. Attack surface: ssl_ca / ssl_certs_dir.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 3.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-apache' . 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
Identify exposure identify
```
grep -r 'puppet-module-puppetlabs-apache' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で puppet-module-puppetlabs-apache を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade puppet-module-puppetlabs-apache to 3.0.0-1
```
ステージング環境で 3.0.0-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:11 puppet-module-puppetlabs-apache

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.0-1"}]}]

Debian:12 puppet-module-puppetlabs-apache

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.0-1"}]}]

Debian:13 puppet-module-puppetlabs-apache

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.0-1"}]}]

References

advisory security-tracker.debian.org