Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.33% for the current model date.
BlackTreeCVE IntelligenceUnknown · Unknown
Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| RubyGemskafo | ECOSYSTEM: introduced 0; fixed 0.3.17 | 0.3.17 | OSV record ↗aggregator derived · 6 Dec 2024 |
| RubyGemskafo | ECOSYSTEM: introduced 0.4.0; fixed 0.5.2 | 0.5.2 | OSV record ↗aggregator derived · 6 Dec 2024 |
Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Fix not verifiedKafo before 0.3.17 and 0.4.x before 0.5.2, as used by Foreman, uses world-readable permissions for default_values.yaml, which allows local users to obtain passwords and other sensitive information by reading the file.
Kafo before 0.3.17 and 0.4.x before 0.5.2, as used by Foreman, uses world-readable permissions for default_values.yaml, which allows local users to obtain passwords and other sensitive information by reading the file.
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may obtain information outside the intended access boundary.
Kafo before 0.3.17 and 0.4.x before 0.5.2, as used by Foreman, uses world-readable permissions for default_values.yaml, which allows local users to obtain passwords and other sensitive information by reading the file.
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may obtain information outside the intended access boundary.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-264. Open the MITRE definition for the exact weakness description.
AV:L/AC:M/Au:N/C:P/I:N/A:NOperational remediation based on structured source evidence.
Published 8 May 2014 · Last source change 6 Aug 2024, 09:05 UTC · CWE-264
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.