# CVE-2019-16572: Jenkins Weibo Plugin stores credentials unencrypted in its global configuration file

> The Jenkins Weibo Plugin stores credentials unencrypted, allowing attackers with file system access to read sensitive information.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Dec 2019
- **Updated:** 9 Aug 2024
- **Also known as:** GHSA-5c97-gxr3-r368

## What is CVE-2019-16572?

CVE-2019-16572 is a medium-severity vulnerability in Jenkins Weibo Plugin, published on 17 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Jenkins Weibo Plugin 1.0.1 and earlier stores credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with access to the master file system.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-1024 (Comparison of Incompatible Types)

## Which versions are affected by CVE-2019-16572?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:weibo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:weibo` | Maven | All versions to 1.0.1 | None |
| `org.jenkins-ci.plugins:weibo` | Maven | All versions to 1.0.1 | None |

Products: Jenkins Weibo.

## How do I fix CVE-2019-16572?

No fix has been published for CVE-2019-16572 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-16572 being exploited?

There is no known exploitation of CVE-2019-16572 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16572 and fix it if it is affected.

What it is: CVE-2019-16572 is a medium-severity vulnerability in Jenkins Weibo Plugin, published on 17 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-16572 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:weibo (Maven): affected all versions up to 1.0.1; no fix listed
- org.jenkins-ci.plugins:weibo (Maven): affected all versions up to 1.0.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-16572/ (Markdown: https://insights.sbomify.com/CVE-2019-16572/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-16572
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-16572
- OSV: https://osv.dev/vulnerability/CVE-2019-16572

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-16572/
Summaries are generated and may contain mistakes; the official description above is the record.