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

CVE-2012-1833 has a CVSS 2.0 base score of 5.0 (Medium). CVSS vector: AV:N/AC:L/Au:N/C:N/I:P/A:N. EPSS exploitation probability: 0.2%.

Is there a public PoC exploit available for CVE-2012-1833?

Yes, a public proof-of-concept exploit is available for CVE-2012-1833. Prioritise patching immediately. EPSS: 0.2%.

Grails CVE-2012-1833

MEDIUM

Permissions, Privileges, and Access Controls (CWE-264)

2012-09-28 cve@mitre.org

Privilege Escalation VMware Grails

5.0

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

5.0 MEDIUM

AV:N/AC:L/Au:N/C:N/I:P/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:L/Au:N/C:N/I:P/A:N

Attack Vector

Network

Attack Complexity

Low

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Sep 28, 2012 - 21:55 cve.org

MEDIUM 5.0

DescriptionCVE.org

VMware SpringSource Grails before 1.3.8, and 2.x before 2.0.2, does not properly restrict data binding, which might allow remote attackers to bypass intended access restrictions and modify arbitrary object properties via a crafted request parameter to an application.

AnalysisAI

VMware SpringSource Grails before 1.3.8, and 2.x before 2.0.2, does not properly restrict data binding, which might allow remote attackers to bypass intended access restrictions and modify arbitrary. Rated medium severity (CVSS 5.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-264. VMware SpringSource Grails before 1.3.8, and 2.x before 2.0.2, does not properly restrict data binding, which might allow remote attackers to bypass intended access restrictions and modify arbitrary object properties via a crafted request parameter to an application. Affected products include: Springsource Grails. Version information: before 1.3.8.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.