dbcve.org
Ptzapp 2Application · Aver

CVE-2023-27055

HIGH · 7.5 CVSS v3.1 Published 2023-03-24
Fix available
A fix is available. Upgrade to 2.0.1051.53 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Aver Information Inc PTZApp2 v20.01044.48 allows attackers to access sensitive files via a crafted GET request.

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

PTZApp2 v20.01044.48 contains a sensitive file disclosure vulnerability allowing remote attackers to access unauthorized files through crafted GET requests. This appears to be a path traversal or insecure direct object reference (IDOR) issue in the web application layer, potentially exposing configuration files, credentials, logs, or other sensitive system data.

MitigationImplement strict input validation and access controls on all GET request handlers to prevent directory traversal; restrict file system access to only explicitly allowed paths and validate all user-supplied path parameters.

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
Ptzapp 2Application
Affected:< 2.0.1051.53

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

CVSS:3.1/AV:N/AC:L/PR:N/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 PTZApp2 is installed
    Check installed programs on Windows (Control Panel > Programs and Features) or look for PTZApp2 in the installation directory (typically C:\Program Files\PTZApp2 or C:\Program Files (x86)\PTZApp2)
    Affected if PTZApp2 is found and the installed version is below 2.0.1051.53
  2. Determine the installed version number
    Right-click the PTZApp2 executable, select Properties, then view the Details tab for the File Version; or open PTZApp2 and check Help > About
    Affected if Version shown is earlier than 2.0.1051.53 (for example, 20.01044.48 as listed in the CVE)
  3. Verify if PTZApp2 web service is running
    Open Services (services.msc) and look for PTZApp2-related web services, or check if port 8080, 80, or 443 is listening (run netstat -ano | findstr :80)
    Affected if The PTZApp2 web interface is exposed and running
  4. Check if remote access is enabled
    Review PTZApp2 settings under Network or Remote Access configuration within the application
    Affected if Remote/web access is enabled, allowing external GET requests
  5. Test for path traversal vulnerability
    If the web interface is accessible, attempt a crafted GET request using directory traversal (for example: http://localhost:8080/../../windows/system32/config/sam or similar path patterns)
    Affected if The server returns file contents outside the intended web root directory

You are affected if PTZApp2 is installed with a version below 2.0.1051.53 AND the web interface is enabled and accessible, allowing unauthorized file access via crafted GET requests.

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.1051.53 or later
Fixed in 2.0.1051.53
Interim mitigation

Implement strict input validation and access controls on all GET request handlers to prevent directory traversal; restrict file system access to only explicitly allowed paths and validate all user-supplied path parameters.

Recommended fix Moderate confidence

PTZApp 2 version 2.0.1051.53 or later

  1. 1. Identify current PTZApp 2 version installed in the environment
  2. 2. Confirm the installed version is below 2.0.1051.53 (vulnerable to CVE-2023-27055)
  3. 3. Obtain PTZApp 2 version 2.0.1051.53 or later from the official Aver Information Inc source
  4. 4. Backup current PTZApp 2 configuration and any custom settings
  5. 5. Uninstall or disable the current vulnerable PTZApp 2 installation
  6. 6. Install PTZApp 2 version 2.0.1051.53 or newer
  7. 7. Restore configuration from backup if needed
  8. 8. Verify the new version is running (2.0.1051.53 or higher)

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

Fix this in Ptzapp 2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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