dbcve.org
Computer Vision Annotation ToolApplication · Intel

CVE-2022-27234

MEDIUM · 6.5 CVSS v3.1 Published 2023-02-16
Fix available
A fix is available. Upgrade to 2.0.1 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
Server-side request forgery in the CVAT software maintained by Intel(R) before version 2.0.1 may allow an authenticated user to potentially enable information disclosure via network access.

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

Server-side request forgery (SSRF) vulnerability in CVAT (Computer Vision Annotation Tool) versions before 2.0.1 allows authenticated users to make the server perform arbitrary network requests, potentially exposing internal services, metadata endpoints, or sensitive internal network resources leading to information disclosure.

MitigationUpgrade CVAT to version 2.0.1 or later. If immediate upgrade is not possible, restrict network access from the CVAT server to internal resources and implement network segmentation to limit exposure.

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
Computer Vision Annotation ToolApplication
Affected:< 2.0.1

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 CVAT installation
    Identify whether CVAT is deployed in your environment by checking for CVAT containers, services, or web applications running on expected ports (typically 8080 for the UI, 9000 for the API). Use 'docker ps' or your container orchestration tools to list running CVAT-related services.
    Affected if CVAT is not present in the environment.
  2. Identify CVAT version
    Retrieve the installed CVAT version from your deployment. If using Docker, check the image tag or digest with 'docker images' or inspect your docker-compose.yml / kubernetes deployment manifests. The version is typically specified in the CVAT image reference.
    Affected if Unable to determine the installed version from deployment configuration.
  3. Compare version to affected range
    Check if the installed version is less than 2.0.1. Compare your identified version number against the threshold 2.0.1, noting that versions like 2.0.0, 1.x.x, or any version string that sorts lower than 2.0.1 are affected.
    Affected if Installed version is less than 2.0.1 (for example, 2.0.0, 1.12.0, etc.).
  4. Verify CVAT authentication status
    Confirm whether user authentication is enabled and functional on your CVAT deployment. Check if the CVAT server is configured to require login credentials for access and whether user registration or invitation features allow new users to be created.
    Affected if Authentication is disabled or the server is exposed to untrusted users who can obtain authenticated access.

You are affected if CVAT is installed with a version lower than 2.0.1 and users can authenticate to the CVAT service.

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

Upgrade CVAT to version 2.0.1 or later. If immediate upgrade is not possible, restrict network access from the CVAT server to internal resources and implement network segmentation to limit exposure.

Recommended fix High confidence

2.0.1

  1. Backup the existing CVAT installation and any associated data
  2. Upgrade CVAT to version 2.0.1 using the appropriate installation method (e.g., Docker, pip, or source installation)
  3. Verify the installation was successful and the version is correct
  4. Test that the application functions normally after the upgrade

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

Fix this in Computer Vision Annotation Tool 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-2022-27234 — 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-2022-27234 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