CVE-2023-31043 Vulnerability Analysis & Exploit Details

CVE-2023-31043
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2023-31043 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2023-31043 Details

Status: Modified

Last updated: 🕔 04 Feb 2025, 17:15 UTC
Originally published on: 🕗 23 Apr 2023, 20:15 UTC

Time between publication and last update: 652 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2023-31043 Vulnerability Summary

CVE-2023-31043: EnterpriseDB EDB Postgres Advanced Server (EPAS) before 14.6.0 logs unredacted passwords in situations where optional parameters are used with CREATE/ALTER USER/GROUP/ROLE, and redacting was configured with edb_filter_log.redact_password_commands. The fixed versions are 10.23.33, 11.18.29, 12.13.17, 13.9.13, and 14.6.0.

Assessing the Risk of CVE-2023-31043

Access Complexity Graph

The exploitability of CVE-2023-31043 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2023-31043

With low attack complexity and no required privileges, CVE-2023-31043 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2023-31043, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2023-31043, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2023-31043 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2023-31043 poses no threat to data integrity.
  • Availability: None
    CVE-2023-31043 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.166% (probability of exploit)

EPSS Percentile: 54.6% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 45.4% of others.

CVE-2023-31043 References

External References

CWE Common Weakness Enumeration

CWE-521

CAPEC Common Attack Pattern Enumeration and Classification

  • Brute Force CAPEC-112 In this attack, some asset (information, functionality, identity, etc.) is protected by a finite secret value. The attacker attempts to gain access to this asset by using trial-and-error to exhaustively explore all the possible secret values in the hope of finding the secret (or a value that is functionally equivalent) that will unlock the asset.
  • Dictionary-based Password Attack CAPEC-16 An attacker tries each of the words in a dictionary as passwords to gain access to the system via some user's account. If the password chosen by the user was a word within the dictionary, this attack will be successful (in the absence of other mitigations). This is a specific instance of the password brute forcing attack pattern. Dictionary Attacks differ from similar attacks such as Password Spraying (CAPEC-565) and Credential Stuffing (CAPEC-600), since they leverage unknown username/password combinations and don't care about inducing account lockouts.
  • Password Brute Forcing CAPEC-49 An adversary tries every possible value for a password until they succeed. A brute force attack, if feasible computationally, will always be successful because it will essentially go through all possible passwords given the alphabet used (lower case letters, upper case letters, numbers, symbols, etc.) and the maximum length of the password.
  • Kerberoasting CAPEC-509 Through the exploitation of how service accounts leverage Kerberos authentication with Service Principal Names (SPNs), the adversary obtains and subsequently cracks the hashed credentials of a service account target to exploit its privileges. The Kerberos authentication protocol centers around a ticketing system which is used to request/grant access to services and to then access the requested services. As an authenticated user, the adversary may request Active Directory and obtain a service ticket with portions encrypted via RC4 with the private key of the authenticated account. By extracting the local ticket and saving it disk, the adversary can brute force the hashed value to reveal the target account credentials.
  • Rainbow Table Password Cracking CAPEC-55 An attacker gets access to the database table where hashes of passwords are stored. They then use a rainbow table of pre-computed hash chains to attempt to look up the original password. Once the original password corresponding to the hash is obtained, the attacker uses the original password to gain access to the system.
  • Remote Services with Stolen Credentials CAPEC-555 This pattern of attack involves an adversary that uses stolen credentials to leverage remote services such as RDP, telnet, SSH, and VNC to log into a system. Once access is gained, any number of malicious activities could be performed.
  • Windows Admin Shares with Stolen Credentials CAPEC-561 An adversary guesses or obtains (i.e. steals or purchases) legitimate Windows administrator credentials (e.g. userID/password) to access Windows Admin Shares on a local machine or within a Windows domain.
  • Password Spraying CAPEC-565 In a Password Spraying attack, an adversary tries a small list (e.g. 3-5) of common or expected passwords, often matching the target's complexity policy, against a known list of user accounts to gain valid credentials. The adversary tries a particular password for each user account, before moving onto the next password in the list. This approach assists the adversary in remaining undetected by avoiding rapid or frequent account lockouts. The adversary may then reattempt the process with additional passwords, once enough time has passed to prevent inducing a lockout.
  • Try Common or Default Usernames and Passwords CAPEC-70 An adversary may try certain common or default usernames and passwords to gain access into the system and perform unauthorized actions. An adversary may try an intelligent brute force using empty passwords, known vendor default credentials, as well as a dictionary of common usernames and passwords. Many vendor products come preconfigured with default (and thus well-known) usernames and passwords that should be deleted prior to usage in a production environment. It is a common mistake to forget to remove these default login credentials. Another problem is that users would pick very simple (common) passwords (e.g. "secret" or "password") that make it easier for the attacker to gain access to the system compared to using a brute force attack or even a dictionary attack using a full dictionary.

Vulnerable Configurations

  • cpe:2.3:a:enterprisedb:postgres_advanced_server:-:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:-:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:8.2:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.4.9:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.4.9:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.5.12:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.5.12:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.6.13:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.6.13:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.7.15:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.7.15:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.8.16:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.8.16:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.9.17:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.9.17:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.10.18:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.10.18:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.11.19:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.11.19:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.12.20:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.12.20:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.13.21:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.13.21:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.14.22:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.14.22:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.14.23:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.14.23:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.15.24:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.15.24:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.16.25:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.16.25:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.17.26:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.17.26:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.17.27:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.17.27:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.18.28:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.18.28:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.19.29:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.19.29:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.20.30:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.20.30:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.21.31:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.21.31:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:10.22.32:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:10.22.32:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.1.7:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.1.7:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.2.9:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.2.9:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.3.10:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.3.10:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.4.11:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.4.11:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.5.12:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.5.12:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.6.13:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.6.13:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.7.14:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.7.14:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.8.15:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.8.15:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.9.16:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.9.16:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.9.17:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.9.17:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.10.19:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.10.19:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.11.20:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.11.20:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.12.21:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.12.21:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.12.22:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.12.22:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.13.23:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.13.23:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.14.24:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.14.24:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.15.25:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.15.25:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.16.26:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.16.26:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:11.17.28:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:11.17.28:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:12.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:12.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:12.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:12.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:12.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:12.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:12.4.5:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:12.4.5:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:12.5.6:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:12.5.6:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:12.6.7:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:12.6.7:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:12.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:12.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:12.7.10:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:12.7.10:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:12.8.12:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:12.8.12:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:12.9.13:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:12.9.13:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:12.10.14:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:12.10.14:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:12.11.15:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:12.11.15:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:12.12.16:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:12.12.16:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:13.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:13.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:13.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:13.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:13.3.6:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:13.3.6:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:13.3.7:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:13.3.7:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:13.4.8:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:13.4.8:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:13.5.9:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:13.5.9:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:13.6.10:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:13.6.10:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:13.7.11:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:13.7.11:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:13.8.12:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:13.8.12:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:14.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:14.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:14.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:14.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:14.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:14.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:14.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:14.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:enterprisedb:postgres_advanced_server:14.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:enterprisedb:postgres_advanced_server:14.5.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-31043: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2024-43107 – Improper Certificate Validation (CWE-295) in the Gallagher Milestone Integration Plugin (MIP) permits unauthenticated messages (e.g. alarm events) ...
  • CVE-2024-41724 – Improper Certificate Validation (CWE-295) in the Gallagher Command Centre SALTO integration allowed an attacker to spoof the SALTO server. Thi...
  • CVE-2025-2133 – A vulnerability classified as problematic was found in ftcms 2.1. Affected by this vulnerability is an unknown functionality of the file /admin/ind...
  • CVE-2025-2132 – A vulnerability classified as critical has been found in ftcms 2.1. Affected is an unknown function of the file /admin/index.php/web/ajax_all_lists...
  • CVE-2025-2131 – A vulnerability was found in dayrui XunRuiCMS up to 4.6.3. It has been rated as problematic. This issue affects some unknown processing of the comp...