What is CVE-2023-31581?

CVE-2023-31581 is a critical-severity use of hard-coded credentials vulnerability in com.usthe.sureness:sureness-core (maven), affecting versions < 1.0.8. It is fixed in 1.0.8. Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact.

How severe is CVE-2023-31581?

CVE-2023-31581 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of com.usthe.sureness:sureness-core are affected by CVE-2023-31581?

com.usthe.sureness:sureness-core (maven) versions < 1.0.8 is affected.

Is there a fix for CVE-2023-31581?

Yes. CVE-2023-31581 is fixed in 1.0.8. Upgrade to this version or later.

Is CVE-2023-31581 exploitable, and should I be worried?

Whether CVE-2023-31581 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-31581 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2023-31581 in com.usthe.sureness:sureness-core

Q: How severe is CVE-2023-31581?

CVE-2023-31581 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of com.usthe.sureness:sureness-core are affected by CVE-2023-31581?

com.usthe.sureness:sureness-core (maven) versions < 1.0.8 is affected.

Q: Is there a fix for CVE-2023-31581?

Yes. CVE-2023-31581 is fixed in 1.0.8. Upgrade to this version or later.

Q: Is CVE-2023-31581 exploitable, and should I be worried?

Whether CVE-2023-31581 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-31581 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-31581?

Upgrade com.usthe.sureness:sureness-core to 1.0.8 or later.

Summary

Sureness uses hardcoded key

Dromara Sureness before v1.0.8 was discovered to use a hardcoded key.

Impact

Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact. Typical impact: unauthorized access using the static credential.

CVE-2023-31581 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.0.8); upgrading removes the vulnerable code path.

Affected versions

com.usthe.sureness:sureness-core (< 1.0.8)

Security releases

com.usthe.sureness:sureness-core → 1.0.8 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade com.usthe.sureness:sureness-core to 1.0.8 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2023-31581? CVE-2023-31581 is a critical-severity use of hard-coded credentials vulnerability in com.usthe.sureness:sureness-core (maven), affecting versions < 1.0.8. It is fixed in 1.0.8. Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact.
How severe is CVE-2023-31581? CVE-2023-31581 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of com.usthe.sureness:sureness-core are affected by CVE-2023-31581? com.usthe.sureness:sureness-core (maven) versions < 1.0.8 is affected.
Is there a fix for CVE-2023-31581? Yes. CVE-2023-31581 is fixed in 1.0.8. Upgrade to this version or later.
Is CVE-2023-31581 exploitable, and should I be worried? Whether CVE-2023-31581 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-31581 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-31581? Upgrade com.usthe.sureness:sureness-core to 1.0.8 or later.