How severe is GHSA-393r-r9mq-g9jv?

GHSA-393r-r9mq-g9jv has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-393r-r9mq-g9jv?

GHSA-393r-r9mq-g9jv affects the following packages: io.jenkins:configuration-as-code (Maven). Ecosystems affected: Maven.

How do I fix GHSA-393r-r9mq-g9jv?

Update io.jenkins:configuration-as-code to 0.8-alpha or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-393r-r9mq-g9jv is resolved across your whole dependency graph.

How do I detect GHSA-393r-r9mq-g9jv in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins:configuration-as-code. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-393r-r9mq-g9jv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-393r-r9mq-g9jv?

O3 pinpoints whether GHSA-393r-r9mq-g9jv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-393r-r9mq-g9jv actively exploited in the wild?

No public exploit code has been indexed for GHSA-393r-r9mq-g9jv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-393r-r9mq-g9jv?

GHSA-393r-r9mq-g9jv is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-393r-r9mq-g9jv published, and has it been updated?

GHSA-393r-r9mq-g9jv was published on May 14, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

GHSA-393r-r9mq-g9jv

MEDIUM

GHSA-393r-r9mq-g9jv is a medium-severity (CVSS 6.5) Information Exposure vulnerability in io.jenkins:configuration-as-code. O3 Security confirms whether GHSA-393r-r9mq-g9jv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Jenkins Configuration as Code Plugin vulnerable to Exposure of Sensitive Information

Also known asCVE-2018-1000609

Published

May 14, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕io.jenkins:configuration-as-code

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A exposure of sensitive information vulnerability exists in Jenkins Configuration as Code Plugin 0.7-alpha and earlier in ConfigurationAsCode.java that allows attackers with Overall/Read access to obtain the YAML export of the Jenkins configuration. Version 0.8-alpha contains a fix for this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.jenkins:configuration-as-code`	all versions	0.8-alpha

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins:configuration-as-code. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update io.jenkins:configuration-as-code to 0.8-alpha or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-393r-r9mq-g9jv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-393r-r9mq-g9jv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-393r-r9mq-g9jv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-393r-r9mq-g9jv in your dependencies?

O3 detects GHSA-393r-r9mq-g9jv across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works