What is CVE-2024-39677?

CVE-2024-39677 is a high-severity SQL injection vulnerability in NHibernate (nuget), affecting versions < 5.4.9. It is fixed in 5.4.9, 5.5.2. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

How severe is CVE-2024-39677?

CVE-2024-39677 has a CVSS score of 5.9 (High). 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 NHibernate are affected by CVE-2024-39677?

NHibernate (nuget) versions < 5.4.9 is affected.

Is there a fix for CVE-2024-39677?

Yes. CVE-2024-39677 is fixed in 5.4.9, 5.5.2. Upgrade to this version or later.

Is CVE-2024-39677 exploitable, and should I be worried?

Whether CVE-2024-39677 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-2024-39677 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-2024-39677?

Upgrade: NHibernate to 5.4.9 or later, NHibernate to 5.5.2 or later.

CVE-2024-39677 in NHibernate

Q: How severe is CVE-2024-39677?

CVE-2024-39677 has a CVSS score of 5.9 (High). 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 NHibernate are affected by CVE-2024-39677?

NHibernate (nuget) versions < 5.4.9 is affected.

Q: Is there a fix for CVE-2024-39677?

Yes. CVE-2024-39677 is fixed in 5.4.9, 5.5.2. Upgrade to this version or later.

Q: Is CVE-2024-39677 exploitable, and should I be worried?

Whether CVE-2024-39677 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-2024-39677 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-2024-39677?

Upgrade: NHibernate to 5.4.9 or later, NHibernate to 5.5.2 or later.

Summary

NHibernate SQL injection vulnerability in discriminator mappings, static fields referenced in HQL, and some utilities

Workarounds

Ensure the application does not use the features listed above.
For discriminator usages, ensure the discriminator values in the mappings do not contain quotes for string discriminators. Furthermore, for types which ToString conversion can be altered to include SQL injections through adequate hacking of the current culture settings, either change for another type, or ensure the used values cannot allow culture exploits, or ensure the application performs sanity checks of the current culture settings. Types sensitive to culture include integers for negative values, dates, times and datetimes, floats and decimals.

References

Impact

A SQL injection vulnerability exists in some types implementing ILiteralType.ObjectToSQLString. Callers of these methods are exposed to the vulnerability, which includes:

Mappings using inheritance with discriminator values:
- The discriminator value could be written in the mapping in a way exploiting the vulnerability of the associated discriminator type, if that type is among the vulnerable ones.
- The current culture settings for formatting the discriminator value type could be altered in a way resulting into SQL injections with the discriminator values.
HQL queries referencing a static field of the application.
Users of the SqlInsertBuilder and SqlUpdateBuilder utilities, calling their AddColumn overload taking a literal value. These overloads are unused by NHibernate but could be used by users referencing directly these utilities.
Any direct use of the ObjectToSQLString methods for building SQL queries on the user side.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2024-39677 has a CVSS score of 5.9 (High). 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 (5.4.9, 5.5.2); upgrading removes the vulnerable code path.

Affected versions

NHibernate (< 5.4.9) NHibernate (>= 5.5.0, < 5.5.2)

Security releases

NHibernate → 5.4.9 (nuget) NHibernate → 5.5.2 (nuget)

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

Releases 5.4.9 and 5.5.2.

Frequently Asked Questions

What is CVE-2024-39677? CVE-2024-39677 is a high-severity SQL injection vulnerability in NHibernate (nuget), affecting versions < 5.4.9. It is fixed in 5.4.9, 5.5.2. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
How severe is CVE-2024-39677? CVE-2024-39677 has a CVSS score of 5.9 (High). 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 NHibernate are affected by CVE-2024-39677? NHibernate (nuget) versions < 5.4.9 is affected.
Is there a fix for CVE-2024-39677? Yes. CVE-2024-39677 is fixed in 5.4.9, 5.5.2. Upgrade to this version or later.
Is CVE-2024-39677 exploitable, and should I be worried? Whether CVE-2024-39677 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-2024-39677 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-2024-39677?
- Upgrade NHibernate to 5.4.9 or later
- Upgrade NHibernate to 5.5.2 or later