Sage XRT Treasury, version 3, fails to properly restrict database access to authorized users, which may enable any authenticated user to gain full access to privileged database functions

CVE-2017-3183

Assigned byThe organization (CNA) that assigned this CVE ID and published the record, usually the vendor.
CERT/CC (opens in new tab)
Published
Last modified
NVD status
Modified
CVSS 3.08.8High

Description

Sage XRT Treasury, version 3, fails to properly restrict database access to authorized users, which may enable any authenticated user to gain full access to privileged database functions. Sage XRT Treasury is a business finance management application. Database user access privileges are determined by the USER_CODE field associated with the querying user. By modifying the USER_CODE value to match that of a privileged user, a low-privileged, authenticated user may gain privileged access to the SQL database. A remote, authenticated user can submit specially crafted SQL queries to gain privileged access to the application database.

Exploitation

Whether attackers are exploiting this vulnerability, and how likely they are to try in the next 30 days.

FIRST Exploit Prediction Scoring System (EPSS)About EPSS (opens in new tab)

FIRST's estimate of the chance attackers try to exploit this vulnerability in the next 30 days.

Probability of exploitationIt predicts attempts, not success, and is updated daily.
2.089%
Compared with other CVEs
At or above 82.073% of scored CVEs
Scored

Affected products

The products and versions with the vulnerability.

Listed by CNA

The products and versions affected, according to the organization that published this CVE.

VendorProductAffected versions
SageXRT Treasury
  • 3

How to fix the vulnerability, or reduce the risk until you can.

Solutions

From CERT/CC, which published this CVE.

The vendor has indicated that XRT Treasury version 4 addresses this issue. Users are encouraged to update to the latest release and to encrypt connections to the database server.

Severity

How serious the vulnerability is if exploited, scored from 0 to 10 with the CVSS standard (opens in new tab).

  • 8.8 HighCVSS 3.0 · PrimaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by NVD (opens in new tab)
    Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
    Network
    Attack complexityWhether the attack depends on conditions the attacker doesn't control.
    Low
    Privileges requiredThe access the attacker needs before attacking.
    Low
    User interactionWhether someone other than the attacker has to do something, like open a link.
    None
    ScopeWhether the attack can reach beyond the vulnerable component.
    Unchanged
    ConfidentialityHow much data the attacker can read.
    High
    IntegrityHow much data the attacker can change.
    High
    AvailabilityHow much the attacker can disrupt the system or service.
    High

    CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HView in FIRST's calculator (opens in new tab)

  • 6.5 MediumCVSS 2.0 · PrimaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by NVD (opens in new tab)
    Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
    Network
    Attack complexityWhether the attack depends on conditions the attacker doesn't control.
    Low
    AuthenticationHow many times the attacker has to sign in.
    Single
    ConfidentialityHow much data the attacker can read.
    Partial
    IntegrityHow much data the attacker can change.
    Partial
    AvailabilityHow much the attacker can disrupt the system or service.
    Partial

    AV:N/AC:L/Au:S/C:P/I:P/A:PView in NVD's calculator (opens in new tab)

Weaknesses and attack patterns

The type of bug behind the vulnerability, and how attackers exploit that type.

  • Authorization Bypass Through User-Controlled Key · CWE-639 (opens in new tab)

    The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

    Likelihood of exploitHow likely MITRE rates attacks on this type of weakness, in general rather than for this vulnerability.
    High
    Abstraction
    Base
    Mapping guidance
    Allowed
    Part of
  • Incorrect Authorization · CWE-863 (opens in new tab)

    The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

    Likelihood of exploitHow likely MITRE rates attacks on this type of weakness, in general rather than for this vulnerability.
    High
    Abstraction
    Class
    Mapping guidance
    Allowed with review
    Part of

References

Advisories, patches, exploits and more about this vulnerability.

This product uses the NVD API but is not endorsed or certified by the NVD (opens in new tab). CVE records from the CVE List (opens in new tab), weakness types from MITRE's CWE (opens in new tab)™ and attack patterns from its CAPEC (opens in new tab)™ are © The MITRE Corporation, used under the CVE (opens in new tab), CWE (opens in new tab) and CAPEC (opens in new tab) terms of use. Known exploited vulnerabilities and SSVC assessments are from CISA. Exploit predictions are from FIRST's EPSS (opens in new tab). About this data