Vulnerability Note VU#626420

Pearson ProctorCache contains hard coded credentials

Original Release date: 16 Jun 2015 | Last revised: 16 Jun 2015


The Pearson ProctorCache software uses a hard coded password for administrative tasks.


The ProctorCache is designed to cache the testing content, as well as cache the responses and maintain a client list of active test-takers. ProctorCache is a server software package installed locally within the LAN on a Windows system.

CWE-259: Use of Hard-coded Password - CVE-2015-0972

ProctorCache prior to version 2015.1.17 requires authentication to perform administrative tasks. However, the authentication consists of a hard-coded administrative password, which is not unique per installation, and cannot be changed.


An attacker on the local network can use the credentials to interrupt a test session and perform administrative tasks such as canceling tests or deleting users. According to Pearson, the actual test data is encrypted and not immediately accessible by an administrator.


Apply an update

Pearson has released ProctorCache version 2015.1.17 to address this issue by allowing the password to be changed. Affected users will be notified directly by Pearson of the update, and should update their software to version 2015.1.17 or later as soon as possible. The location of the upgrade as well as instructions for changing the ProctorCache password will be provided for download in the notification to existing customers.

Vendor Information (Learn More)

VendorStatusDate NotifiedDate Updated
Pearson EducationAffected23 Jan 201516 Jun 2015
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base 6.2 AV:A/AC:L/Au:S/C:N/I:P/A:C
Temporal 5.1 E:F/RL:OF/RC:C
Environmental 1.3 CDP:ND/TD:L/CR:ND/IR:ND/AR:ND



This document was written by Garret Wassermann.

Other Information

  • CVE IDs: CVE-2015-0972
  • Date Public: 15 Jun 2015
  • Date First Published: 16 Jun 2015
  • Date Last Updated: 16 Jun 2015
  • Document Revision: 64


If you have feedback, comments, or additional information about this vulnerability, please send us email.