How severe is CVE-2023-33000?

CVE-2023-33000 has a CVSS score of 3.1/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-33000?

CVE-2023-33000 affects the following packages: io.jenkins.plugins:cavisson-ns-nd-integration (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-33000?

Update io.jenkins.plugins:cavisson-ns-nd-integration to 4.11.0.48 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-33000 is resolved across your whole dependency graph.

How do I detect CVE-2023-33000 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:cavisson-ns-nd-integration, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-33000 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.

Is CVE-2023-33000 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-33000 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 is the EPSS score for CVE-2023-33000?

CVE-2023-33000 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-33000?

CVE-2023-33000 is classified as CWE-522 (CWE-522). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-33000 published, and has it been updated?

CVE-2023-33000 was published on May 16, 2023 and was last updated on February 16, 2024. 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

LOW severity

CVE-2023-33000 — cavisson-ns-nd-integration

LOW

CVE-2023-33000 is a low-severity (CVSS 3.1) CWE-522 vulnerability in io.jenkins.plugins:cavisson-ns-nd-integration. A fix is available for io.jenkins.plugins:cavisson-ns-nd-integration — see the affected versions and patch details below.

Jenkins NS-ND Integration Performance Publisher Plugin displays credentials without masking

Published

May 16, 2023

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-33000.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕io.jenkins.plugins:cavisson-ns-nd-integration

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

Jenkins NS-ND Integration Performance Publisher Plugin stores credentials in job config.xml files on the Jenkins controller as part of its configuration.

While these credentials are stored encrypted on disk, in NS-ND Integration Performance Publisher Plugin 4.8.0.149 and earlier, the job configuration form does not mask these credentials, increasing the potential for attackers to observe and capture them.

NS-ND Integration Performance Publisher Plugin 4.11.0.48 masks credentials displayed on the configuration form.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.jenkins.plugins:cavisson-ns-nd-integration`	all versions	4.11.0.48`io.jenkins.plugins:cavisson-ns-nd-integration:4.11.0.48`

Affected Products

1 product · 1 configurations

Application

ns-nd integration performance publisherjenkins

≤ 4.8.0.149

range

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.plugins:cavisson-ns-nd-integration, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.plugins:cavisson-ns-nd-integration to 4.11.0.48 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-33000 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.

Frequently Asked Questions

Jenkins NS-ND Integration Performance Publisher Plugin stores credentials in job config.xml files on the Jenkins controller as part of its configuration. While these credentials are stored encrypted on disk, in NS-ND Integration Performance Publisher Plugin 4.8.0.149 and earlier, the job configuration form does not mask these credentials, increasing the potential for attackers to observe and capture them. NS-ND Integration Performance Publisher Plugin 4.11.0.48 masks credentials displayed on the configuration form.

O3 Security · Impact-Aware SCA

Is CVE-2023-33000 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

3.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

CWE Classification

CWE-522CWE-522

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

May 16, 2023

Last updated

Feb 16, 2024

Identifiers

CVE-2023-33000

References

Advisorynvd.nist.gov · CVE 2023 33000 Webjenkins.io · 2023 05 16

Related vulnerabilities

Also affects cavisson-ns-nd-integration

This CVE is low severity; 6 of 6 other CVEs affecting cavisson-ns-nd-integration are rated as high or higher (top: high).

CVE-2022-45391CVE-2022-45392CVE-2022-41229CVE-2022-41228CVE-2022-41227CVE-2022-34191

Same weakness: CWE-522

This CVE is low severity; 2 of 2 other CVEs with CWE-522 are rated as high or higher (top: critical).

CVE-2026-105769CVE-2026-118763Browse all CWE-522

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

CVE-2023-33000 — cavisson-ns-nd-integration

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2023-33000 in your dependencies?