Comparison Overview

Utah Gun Exchange LLC

VS

Rover.com

Utah Gun Exchange LLC

1231 W. South Jordan Pkwy. (10400 S.), South Jordan, Utah, US, 84095
Last Update: 2025-12-27

Utah Gun Exchange is the best place online for Utah residents to buy and sell their firearms, ammo, and accessories. It doesn't cost a thing, just sign up and post your ad! With dozens of listings be added each day, you are sure to find what you are looking for or find someone looking to buy your items. http://www.utahgunexchange.com/

NAICS: 81
NAICS Definition: Other Services (except Public Administration)
Employees: 1
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
1

Rover.com

720 Olive Way, Seattle, Washington, US, 98101
Last Update: 2025-12-25
Between 750 and 799

At Rover, everyone has ownership of their work and the opportunity to make a true impact. We believe that being diverse and inclusive is key to our success and encourage every employee to share their unique perspective while being their true self. We believe everyone deserves the unconditional love of a pet, and Rover exists to make it easier to experience that love. We’re supporting dog owners and empowering dog sitters to run thriving pet-care businesses in your neighborhoods. The Rover app and website connect dog and cat parents with loving pet sitters and dog walkers in neighborhoods across the US, Canada, and Europe.

NAICS: 81
NAICS Definition: Other Services (except Public Administration)
Employees: 11,132
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/utah-gun-exchange-llc.jpeg
Utah Gun Exchange LLC
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/roverdotcom.jpeg
Rover.com
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Utah Gun Exchange LLC
100%
Compliance Rate
0/4 Standards Verified
Rover.com
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Consumer Services Industry Average (This Year)

No incidents recorded for Utah Gun Exchange LLC in 2025.

Incidents vs Consumer Services Industry Average (This Year)

No incidents recorded for Rover.com in 2025.

Incident History — Utah Gun Exchange LLC (X = Date, Y = Severity)

Utah Gun Exchange LLC cyber incidents detection timeline including parent company and subsidiaries

Incident History — Rover.com (X = Date, Y = Severity)

Rover.com cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/utah-gun-exchange-llc.jpeg
Utah Gun Exchange LLC
Incidents

Date Detected: 7/2020
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/roverdotcom.jpeg
Rover.com
Incidents

No Incident

FAQ

Rover.com company demonstrates a stronger AI Cybersecurity Score compared to Utah Gun Exchange LLC company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Utah Gun Exchange LLC company has historically faced a number of disclosed cyber incidents, whereas Rover.com company has not reported any.

In the current year, Rover.com company and Utah Gun Exchange LLC company have not reported any cyber incidents.

Neither Rover.com company nor Utah Gun Exchange LLC company has reported experiencing a ransomware attack publicly.

Utah Gun Exchange LLC company has disclosed at least one data breach, while the other Rover.com company has not reported such incidents publicly.

Neither Rover.com company nor Utah Gun Exchange LLC company has reported experiencing targeted cyberattacks publicly.

Neither Utah Gun Exchange LLC company nor Rover.com company has reported experiencing or disclosing vulnerabilities publicly.

Neither Utah Gun Exchange LLC nor Rover.com holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Utah Gun Exchange LLC company nor Rover.com company has publicly disclosed detailed information about the number of their subsidiaries.

Rover.com company employs more people globally than Utah Gun Exchange LLC company, reflecting its scale as a Consumer Services.

Neither Utah Gun Exchange LLC nor Rover.com holds SOC 2 Type 1 certification.

Neither Utah Gun Exchange LLC nor Rover.com holds SOC 2 Type 2 certification.

Neither Utah Gun Exchange LLC nor Rover.com holds ISO 27001 certification.

Neither Utah Gun Exchange LLC nor Rover.com holds PCI DSS certification.

Neither Utah Gun Exchange LLC nor Rover.com holds HIPAA certification.

Neither Utah Gun Exchange LLC nor Rover.com holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.

Risk Information
cvss3
Base: 5.9
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
Description

A vulnerability has been found in jackq XCMS up to 3fab5342cc509945a7ce1b8ec39d19f701b89261. Affected is the function Upload of the file Admin/Home/Controller/ProductImageController.class.php of the component Backend. Such manipulation of the argument File leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The project was informed of the problem early through an issue report but has not responded yet.

Risk Information
cvss2
Base: 5.8
Severity: LOW
AV:N/AC:L/Au:M/C:P/I:P/A:P
cvss3
Base: 4.7
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L
cvss4
Base: 5.1
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

In PHP versions 8.1.* before 8.1.34, 8.2.* before 8.2.30, 8.3.* before 8.3.29, 8.4.* before 8.4.16, 8.5.* before 8.5.1 when using the PDO PostgreSQL driver with PDO::ATTR_EMULATE_PREPARES enabled, an invalid character sequence (such as \x99) in a prepared statement parameter may cause the quoting function PQescapeStringConn to return NULL, leading to a null pointer dereference in pdo_parse_params() function. This may lead to crashes (segmentation fault) and affect the availability of the target server.

Risk Information
cvss4
Base: 8.2
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

In PHP versions:8.1.* before 8.1.34, 8.2.* before 8.2.30, 8.3.* before 8.3.29, 8.4.* before 8.4.16, 8.5.* before 8.5.1, a heap buffer overflow occurs in array_merge() when the total element count of packed arrays exceeds 32-bit limits or HT_MAX_SIZE, due to an integer overflow in the precomputation of element counts using zend_hash_num_elements(). This may lead to memory corruption or crashes and affect the integrity and availability of the target server.

Risk Information
cvss3
Base: 6.5
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H
Description

In PHP versions:8.1.* before 8.1.34, 8.2.* before 8.2.30, 8.3.* before 8.3.29, 8.4.* before 8.4.16, 8.5.* before 8.5.1, the getimagesize() function may leak uninitialized heap memory into the APPn segments (e.g., APP1) when reading images in multi-chunk mode (such as via php://filter). This occurs due to a bug in php_read_stream_all_chunks() that overwrites the buffer without advancing the pointer, leaving tail bytes uninitialized. This may lead to information disclosure of sensitive heap data and affect the confidentiality of the target server.

Risk Information
cvss4
Base: 6.3
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X