dbcve.org
AptareApplication · Veritas

CVE-2020-12874

CRITICAL · 9.8 CVSS v3.1 Published 2020-05-14
Fix available
A fix is available. Upgrade to 10.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Veritas APTARE versions prior to 10.4 included code that bypassed the normal login process when specific authentication credentials were provided to the server.

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

Veritas APTARE versions prior to 10.4 contain an authentication bypass vulnerability where specific hardcoded or backdoor credentials bypass the normal login mechanism, allowing unauthenticated attackers to gain administrative access to the platform.

MitigationUpgrade Veritas APTARE to version 10.4 or later to remediate the authentication bypass. If immediate patching is not possible, restrict network access to the APTARE server and monitor for unauthorized access using the affected credentials.

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
AptareApplication
Affected:< 10.4

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify if Veritas APTARE is installed
    Check for APTARE installation directories (typically under /opt/veritas or similar), or look for aptare-related services or processes running on the system using commands like 'ps aux | grep -i aptare' or 'ls -la /opt/veritas/'
    Affected if APTARE software is found running on the system
  2. Determine the installed APTARE version
    Locate the APTARE version information - this is typically found in the product's about page, in installation logs, or in a version file within the APTARE installation directory. Common locations include the admin web interface or a version.info file in the installation root
    Affected if The installed version is anything less than 10.4 (e.g., 10.3.x, 10.2.x, etc.)
  3. Verify the APTARE admin web interface is accessible
    Check if the APTARE web console port (typically ports 80, 443, or 8443) is listening and accessible on the server using 'netstat -tlnp | grep -E "80|443|8443"' or similar network inspection tools
    Affected if The APTARE web administration interface is exposed and responds to requests
  4. Confirm the login mechanism accepts hardcoded credentials
    Attempt to access the APTARE login portal via browser or API tool. The vulnerability allows authentication bypass using specific hardcoded credentials - however, for detection purposes, confirm the login page is reachable and the application responds to authentication attempts
    Affected if The login portal is reachable over the network and accepts authentication attempts, combined with a version prior to 10.4

The environment is affected if Veritas APTARE is installed with a version lower than 10.4 and the admin web interface is network-accessible, allowing potential exploitation via the hardcoded credentials.

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

Upgrade Veritas APTARE to version 10.4 or later to remediate the authentication bypass. If immediate patching is not possible, restrict network access to the APTARE server and monitor for unauthorized access using the affected credentials.

Recommended fix High confidence

10.4

  1. Back up the current APTARE installation and any associated databases
  2. Upgrade APTARE to version 10.4
  3. After upgrade, verify that the normal authentication process is enforced and there are no bypass mechanisms
  4. Confirm the upgrade was successful by testing login functionality

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

Fix this in Aptare 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-2020-12874 — 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-2020-12874 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