What is the CVSS score of CVE-2012-2604?

CVE-2012-2604 has a CVSS 2.0 base score of 3.5 (Low). CVSS vector: AV:N/AC:M/Au:S/C:N/I:P/A:N. EPSS exploitation probability: 1.7%.

Network Sentry Appliance Software CVE-2012-2604

LOW

Cross-site Scripting (XSS) (CWE-79)

2012-06-13 cret@cert.org

XSS Network Sentry Appliance Software Network Sentry Appliance

3.5

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

3.5 LOW

AV:N/AC:M/Au:S/C:N/I:P/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:M/Au:S/C:N/I:P/A:N

Attack Vector

Network

Attack Complexity

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Jun 13, 2012 - 15:55 cve.org

LOW 3.5

DescriptionCVE.org

Multiple cross-site scripting (XSS) vulnerabilities in GuestAccess.jsp in the Guest/Contractor access component in the administrative interface in Bradford Network Sentry before 5.3.3 allow remote authenticated users to inject arbitrary web script or HTML via unspecified fields.

AnalysisAI

Multiple cross-site scripting (XSS) vulnerabilities in GuestAccess.jsp in the Guest/Contractor access component in the administrative interface in Bradford Network Sentry before 5.3.3 allow remote. Rated low severity (CVSS 3.5), this vulnerability is remotely exploitable. No vendor patch available.

Technical ContextAI

This vulnerability is classified as Cross-Site Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. Multiple cross-site scripting (XSS) vulnerabilities in GuestAccess.jsp in the Guest/Contractor access component in the administrative interface in Bradford Network Sentry before 5.3.3 allow remote authenticated users to inject arbitrary web script or HTML via unspecified fields. Affected products include: Bradfordnetworks Network Sentry Appliance Software, Bradfordnetworks Network Sentry Appliance. Version information: before 5.3.3.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.