Skip to content

← Public intelligence

NuGet package

serenity.net.web

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.3NuGetPublished

    User account enumeration in Serenity

    CVE-2023-31286 · GHSA-w7jm-9x4m-8qc3

    Affected
    • NuGet serenity.net.web < 6.7.0
    Fixed in
    6.7.0· Vendor fix available
    Issue
    An issue was discovered in Serenity Serene (and StartSharp) before 6.7.0. When a password reset request occurs, the server response leaks the existence of users. If one tries to reset a password of a non-existent user, an error message indicates that this user does not exist.

    Recommended action: Upgrade to 6.7.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.8NuGetPublished

    Insufficient token expiration in Serenity

    CVE-2023-31287 · GHSA-2hp9-3xfr-r9w2

    Affected
    • NuGet serenity.net.web < 6.7.0
    Fixed in
    6.7.0· Vendor fix available
    Issue
    An issue was discovered in Serenity Serene (and StartSharp) before 6.7.0. Password reset links are sent by email. A link contains a token that is used to reset the password. This token remains valid even after the password reset and can be used a second time to change the password of the corresponding user. The token expires only 3 hours after issuance and is sent as a query parameter when resetting. An attacker with access to the browser history can thus use the token again to change the password in order to take over the account.

    Recommended action: Upgrade to 6.7.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →