What is the CVSS score of CVE-2016-3046?

CVE-2016-3046 has a CVSS 3.0 base score of 2.7 (Low). CVSS vector: CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.1%.

Is there a patch available for CVE-2016-3046?

Yes, a patch is available for CVE-2016-3046. Update the affected software to the latest version immediately.

Security Access Manager For Web 8 0 Firmware CVE-2016-3046

LOW

SQL Injection (CWE-89)

2017-02-01 psirt@us.ibm.com

SQLi IBM Security Access Manager For Web 8 0 Firmware Security Access Manager For Mobile Security Access Manager 9 0 Firmware

2.7

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

2.7 LOW

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Feb 01, 2017 - 20:59 cve.org

LOW 2.7

DescriptionCVE.org

IBM Security Access Manager for Web is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements which could allow the attacker to view information in the back-end database.

AnalysisAI

IBM Security Access Manager for Web is vulnerable to SQL injection. Rated low severity (CVSS 2.7), this vulnerability is remotely exploitable, low attack complexity.

Technical ContextAI

This vulnerability is classified as SQL Injection (CWE-89), which allows attackers to execute arbitrary SQL commands against the database. IBM Security Access Manager for Web is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements which could allow the attacker to view information in the back-end database. Affected products include: Ibm Security Access Manager For Web 8.0 Firmware, Ibm Security Access Manager For Mobile, Ibm Security Access Manager 9.0 Firmware.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use parameterized queries/prepared statements. Never concatenate user input into SQL. Apply least-privilege database permissions.