dbcve.org
Remedy Action Request SystemApplication · Bmc

CVE-2016-2349

HIGH · 7.5 CVSS v3.0 Published 2016-12-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Remedy AR System Server in BMC Remedy 8.1 SP 2, 9.0, 9.0 SP 1, and 9.1 allows attackers to reset arbitrary passwords via a blank previous password.

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

BMC Remedy AR System Server contains a password reset vulnerability where the system accepts a blank previous password when processing password change requests, allowing unauthenticated attackers to reset passwords for arbitrary user accounts by manipulating the password reset form.

MitigationApply available vendor patches for BMC Remedy AR System Server. Until patches are applied, consider restricting network access to the AR System Server and monitoring for unauthorized password reset activity.

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
Remedy Action Request SystemApplication
Affected:= 8.1= 9.0= 9.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 BMC Remedy AR System Server installation and version
    Locate the AR System Server installation directory and check the version. Typically found in installation logs, the AR System administration console, or by querying the AR System server properties. On Windows, check the AR System installation path (commonly C:\Program Files\BMC Software\ARSystem or similar). On Linux/Unix, check /opt/bmc/ARSystem or the configured installation directory. Run 'ardb -version' or check version.xml in the server conf directory if available.
    Affected if The installed version matches 8.1, 9.0, or 9.1 exactly (or falls within these version ranges if the = notation indicates version lines).
  2. Confirm password reset web interface is exposed
    Identify if the AR System web portal (AR System Mid Tier) is accessible. Check if the password reset form endpoint is reachable. Typically accessible via URLs like /arsys/forms/ or /armidtier/. Verify network accessibility by attempting to access the password reset URL from an unauthorized network location.
    Affected if The password reset form is accessible from the network without authentication.
  3. Review AR System logs for password reset activity with blank previous passwords
    Examine AR System server logs (typically found in the logs directory under the AR System installation, such as arserver.log, arerror.log, or audit logs). Search for password change or password reset events. Look for entries where the previous password field is empty or null during password modification operations.
    Affected if Logs show password reset or password change requests where the previous password value is blank, null, or missing.
  4. Check for unauthorized user account password modifications
    Review AR System audit logs or user management logs for password changes on user accounts that were not initiated by the legitimate user or administrator. Look for patterns of password resets for multiple accounts, especially administrative accounts, occurring in short time periods.
    Affected if Audit logs reveal password changes for accounts that were not authorized by the account owner or administrator.

Your environment is affected if BMC Remedy AR System Server version 8.1, 9.0, or 9.1 is installed and the password reset functionality is network-accessible, particularly if logs show password changes with blank previous password values or unauthorized account password modifications.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available vendor patches for BMC Remedy AR System Server. Until patches are applied, consider restricting network access to the AR System Server and monitoring for unauthorized password reset activity.

Fix this in Remedy Action Request System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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