dbcve.org
Ezd RpApplication · Nask

CVE-2024-7267

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-07
Fix available
A fix is available. Upgrade to 19.6 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
Exposure of Sensitive Information vulnerability in Naukowa i Akademicka Sieć Komputerowa - Państwowy Instytut Badawczy EZD RP allows logged-in user to retrieve information about IP infrastructure and credentials. This issue affects EZD RP all versions before 19.6

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

The vulnerability in EZD RP allows any logged-in user to retrieve sensitive information including IP infrastructure details and credentials. This indicates improper access controls or information leakage where authenticated users can access data beyond their authorized scope, potentially exposing network topology and authentication materials.

MitigationUpgrade EZD RP to version 19.6 or later to remediate the vulnerability. Additionally, assess and rotate any credentials that may have been exposed due to this flaw.

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
Ezd RpApplication
Affected:< 19.6

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. Identify if EZD RP is installed
    Check the system for Nask EZD RP software installation - look for the application or its service process running on the server or check installed programs list
    Affected if EZD RP software is present on the system
  2. Determine the installed version of EZD RP
    Access the application management interface or check the software version information typically found in the application about screen, installation directory, or system services
    Affected if The installed version is below 19.6 (e.g., 19.5, 19.4, earlier versions)
  3. Verify user authentication is enabled
    Check if user login functionality is active in the EZD RP configuration or administration settings - the flaw affects any logged-in user
    Affected if User authentication is enabled and users can log in to the application
  4. Confirm network exposure
    Determine if the EZD RP interface is accessible over the network or the internet - assess whether unauthenticated or low-privilege network users could potentially obtain login credentials
    Affected if The application is network-accessible beyond the intended admin-only segment

You are affected if EZD RP version 19.6 or later is NOT installed AND user authentication is enabled in your environment.

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

Upgrade EZD RP to version 19.6 or later to remediate the vulnerability. Additionally, assess and rotate any credentials that may have been exposed due to this flaw.

Recommended fix Moderate confidence

19.6

  1. Verify current EZD RP version by checking the application administration panel or system information
  2. Review the official EZD RP release notes and upgrade documentation from NASK-PIB (naukowa.pl) for version 19.6
  3. Create a complete backup of the EZD RP database and configuration files before proceeding
  4. Plan maintenance window as upgrade may require system downtime
  5. Download EZD RP version 19.6 or later from the official vendor distribution channel
  6. Execute the upgrade following the vendor's documented migration procedure
  7. Verify the upgrade was successful by logging in and confirming system functionality
  8. After upgrade, verify the vulnerability is remediated by confirming sensitive IP infrastructure and credential information is no longer exposed

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

Fix this in Ezd Rp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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