Cyber Resilience

CVE-2023-40349

Jenkins Gogs ≤ 1.0.15

Published
16 August 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0058 45th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2023-40349 is a medium-severity Improper Initialization (CWE-665) vulnerability in Jenkins Gogs. Its CVSS base score is 5.3 (Medium).

Operationally, ranked at the 45th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Jenkins Gogs Plugin 1.0.15 and earlier improperly initializes an option to secure its webhook endpoint, allowing unauthenticated attackers to trigger builds of jobs.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-46657Same product: Jenkins Gogs
CVE-2023-40348Same product: Jenkins Gogs
CVE-2026-48923Same vendor: Jenkins
CVE-2023-50766Same vendor: Jenkins
CVE-2024-23900Same vendor: Jenkins
CVE-2024-23902Same vendor: Jenkins
CVE-2025-64141Same vendor: Jenkins
CVE-2024-23904Same vendor: Jenkins
CVE-2025-53672Same vendor: Jenkins
CVE-2026-57305Same vendor: Jenkins

Affected Assets

jenkins
gogs
≤ 1.0.15

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-665

Ensures shared resources are explicitly initialized or cleared on allocation, preventing exposure of prior contents to new users or processes.

addresses: CWE-665

Mandates that every instance begins in a known (presumably clean) state, eliminating reliance on residual or uninitialized state left by prior executions.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce proper resource initialization during coding and testing.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect uninitialized variables but does not itself enforce initialization practices.

prevents

Configuration management can enforce secure defaults and initialization settings but is not the primary control for code-level initialization.

prevents

Secure development life cycle mandates initialization checks and secure defaults that directly prevent improper resource initialization.

prevents

Secure system architecture and engineering principles require explicit initialization of resources and secure state management.

prevents

Secure coding standards explicitly forbid uninitialized variables and mandate proper resource initialization before use.

References