dbcve.org
Notes Station 3Application · Qnap

CVE-2024-38645

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-22
Fix available
A fix is available. Upgrade to 3.9.7 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
A server-side request forgery (SSRF) vulnerability has been reported to affect Notes Station 3. If exploited, the vulnerability could allow remote authenticated attackers to read application data. We have already fixed the vulnerability in the following version: Notes Station 3 3.9.7 and later

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

This is a Server-Side Request Forgery (SSRF) vulnerability in Notes Station 3 that allows authenticated remote attackers to make the application perform unintended requests to internal or external resources, potentially reading sensitive application data. SSRF arises when applications fetch remote resources based on user-controlled input without proper validation.

MitigationUpgrade Notes Station 3 to version 3.9.7 or later. If immediate upgrade is not feasible, implement network segmentation and restrict the application's ability to make outbound requests.

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
Notes Station 3Application
Affected:>= 3.9.0, < 3.9.7

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Confirm Notes Station 3 is installed
    Access QNAP NAS admin interface, go to App Center or Control Panel, and verify Notes Station 3 application is present and running
    Affected if Notes Station 3 is not installed on the system
  2. Check installed version number
    In QNAP admin interface, right-click Notes Station 3 in App Center or view its details to see the version number. Compare against the affected range: 3.9.0 <= version < 3.9.7
    Affected if Installed version is 3.9.0 through 3.9.6 inclusive
  3. Verify Notes Station 3 web interface is network accessible
    Attempt to access Notes Station 3 web portal via browser at typical URLs such as https://[nas-ip]:[port]/notes or check QNAP portal configuration for Notes Station 3 access
    Affected if The web interface is exposed to network and reachable by potential attackers
  4. Confirm user authentication is configured
    Check Notes Station 3 security settings to verify user authentication is required for access. Examine if anonymous or guest access is enabled
    Affected if Authentication is disabled or weak, allowing unauthenticated attackers to reach the vulnerable feature

System is affected if Notes Station 3 version is between 3.9.0 and 3.9.6 inclusive AND the web interface is network-accessible with valid authentication available to potential attackers.

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 3.9.7 or later
Fixed in 3.9.7
Interim mitigation

Upgrade Notes Station 3 to version 3.9.7 or later. If immediate upgrade is not feasible, implement network segmentation and restrict the application's ability to make outbound requests.

Recommended fix High confidence

Notes Station 3 version 3.9.7

  1. 1. Back up all Notes Station 3 data before upgrading.
  2. 2. Log in to the QNAP NAS admin interface.
  3. 3. Navigate to the Notes Station 3 application settings.
  4. 4. Check the current version (verify it is >= 3.9.0 and < 3.9.7).
  5. 5. Locate the update option within the application or QNAP App Center.
  6. 6. Update Notes Station 3 to version 3.9.7 or later.
  7. 7. After the update completes, verify the installed version is 3.9.7 or higher.
  8. 8. Test that Notes Station 3 functionality is working correctly.

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

Fix this in Notes Station 3 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38645 — 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-38645 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