dbcve.org
S NotifyApplication · Savignano

CVE-2024-23737

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-01
Fix available
A fix is available. Upgrade to 2.0.1 / 4.0.2 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross Site Request Forgery (CSRF) vulnerability in savignano S/Notify before 4.0.2 for Jira allows attackers to allows attackers to manipulate a user's S/MIME certificate of PGP key via malicious link or email.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

CSRF vulnerability in savignano S/Notify plugin for Jira allows authenticated users to have their S/MIME certificate or PGP key manipulated through malicious links or emails. Attackers can trick users into unknowingly submitting requests that modify their cryptographic key settings, potentially enabling impersonation or man-in-the-middle attacks.

MitigationUpdate S/Notify to version 4.0.2 or later, which includes CSRF protection. Until patched, avoid clicking untrusted links while authenticated in Jira.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
S NotifyApplication
Affected:< 2.0.1< 4.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify S/Notify plugin is installed
    Access Jira Administration > Apps > Manage apps and search for 'S Notify' or 'S/Notify' in the list of installed plugins
    Affected if The S/Notify plugin appears in the installed apps list
  2. Determine installed S/Notify version
    In Jira Administration > Apps > Manage apps, locate S/Notify and note the version number shown in the app details
    Affected if The version is less than 2.0.1, or between 2.0.1 and 4.0.1 (inclusive)
  3. Confirm S/MIME or PGP key configuration exists
    Navigate to the authenticated user's profile settings in Jira where S/Notify cryptographic key options appear (typically under user settings or S/Notify plugin settings), and verify whether an S/MIME certificate or PGP key has been configured
    Affected if The user has configured an S/MIME certificate or PGP key in their S/Notify settings
  4. Check for CSRF protection in plugin
    Review the S/Notify plugin configuration or changelog for CSRF token implementation on key modification forms
    Affected if No CSRF protection tokens are present on forms that modify S/MIME or PGP key settings

A user is affected if S/Notify plugin is installed with a version below 2.0.1 or between 2.0.1 and 4.0.1, and the user has configured an S/MIME certificate or PGP key that could be modified via CSRF.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.1 / 4.0.2 or later
Fixed in 2.0.14.0.2
Interim mitigation

Update S/Notify to version 4.0.2 or later, which includes CSRF protection. Until patched, avoid clicking untrusted links while authenticated in Jira.

Recommended fix High confidence

4.0.2 (or 2.0.1 for the 2.x branch)

  1. Check the current installed version of S Notify plugin in Jira via the Atlassian Marketplace or the Manage Apps section
  2. Identify which version line you are on (2.x or 4.x)
  3. If on version 2.x line: upgrade to version 2.0.1 or later
  4. If on version 4.x line: upgrade to version 4.0.2 or later
  5. After upgrade, clear browser cache and verify the plugin is functioning correctly
  6. Test that S/MIME certificate and PGP key management functions work as expected
Caveat Standard upgrade best practices apply - backup data before upgrading, test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in S Notify Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23737 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23737 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data