dbcve.org
AntivirusApplication · Avira

CVE-2023-1900

MEDIUM · 5.5 CVSS v3.1 Published 2023-04-19
Fix available
A fix is available. Upgrade to 1.0.2303.633 or later.
See remediation →
57/100
Remediation priority · Elevated
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 vulnerability within the Avira network protection feature allowed an attacker with local execution rights to cause an overflow. This could corrupt the data on the heap and lead to a denial-of-service situation. Issue was fixed with Endpointprotection.exe version 1.0.2303.633

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 · high confidence

Heap overflow vulnerability in Avira Endpoint Protection's network protection component allows a local attacker to corrupt heap data and cause denial of service. Requires local execution rights to trigger.

MitigationUpdate Avira Endpoint Protection to version 1.0.2303.633 or later to apply the vendor patch.

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
AntivirusApplication
Affected:< 1.0.2303.633

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

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

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 Avira Antivirus is installed
    Check for Avira installation directory (typically C:\Program Files\Avira\ or C:\Program Files (x86)\Avira\) or look for Avira processes in Task Manager
    Affected if Avira Antivirus is not found on the system, the user is not affected by this CVE
  2. Identify installed Avira version
    Open Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Avira\Avira antivir or check the product's About/Properties window in the Avira UI
    Affected if Version is missing from registry or cannot be determined, proceed to verify via UI or executable version info
  3. Compare version to affected range
    Compare the installed version number to the affected range: versions below 1.0.2303.633 are vulnerable
    Affected if Installed version is less than 1.0.2303.633 (for example, 1.0.2303.500, 1.0.2200.100, etc.)
  4. Verify network protection component status
    Open Avira main UI, go to Network Protection module or check if the 'Avira Web Protection' / 'Network Protection' service is running
    Affected if Network protection component is enabled and active on a vulnerable version

User is affected if Avira Antivirus is installed with a version lower than 1.0.2303.633 and the network protection component is enabled.

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

Update Avira Endpoint Protection to version 1.0.2303.633 or later to apply the vendor patch.

Recommended fix Moderate confidence

Endpointprotection.exe version 1.0.2303.633 or later

  1. 1. Verify the current version of Avira Endpoint Protection installed on the system by opening the Endpoint Protection client or checking Add/Remove Programs
  2. 2. Download the latest version of Avira Endpoint Protection (version 1.0.2303.633 or later) from the official Avira or Norton support website (support.norton.com)
  3. 3. Ensure all active processes and services related to the antivirus are temporarily disabled or the system is in safe mode
  4. 4. Run the installer for version 1.0.2303.633 or newer
  5. 5. Follow the installation wizard prompts to complete the upgrade
  6. 6. Restart the system when prompted to ensure all components are properly initialized
  7. 7. After restart, verify the installed version matches or exceeds 1.0.2303.633 to confirm the fix is applied
Caveat Standard antivirus upgrade risks apply - ensure compatibility with existing system software and backup critical data before upgrading

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

Fix this in Antivirus Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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