CVE-2010-3694 : Detail

CVE-2010-3694

Cross-Site Request Forgery - CSRF
A01-Broken Access Control
0.21%V3
Network
2010-11-09
19h00 +00:00
2011-07-12
07h00 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Cross-site request forgery (CSRF) vulnerability in the Horde Application Framework before 3.3.9 allows remote attackers to hijack the authentication of unspecified victims for requests to a preference form.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-352 Cross-Site Request Forgery (CSRF)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Metrics

Metrics Score Severity CVSS Vector Source
V2 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P nvd@nist.gov

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Products Mentioned

Configuraton 0

Horde>>Horde_application_framework >> Version To (including) 3.3.8

Horde>>Horde_application_framework >> Version 1.0.3

Horde>>Horde_application_framework >> Version 1.1.1

Horde>>Horde_application_framework >> Version 1.3.0

Horde>>Horde_application_framework >> Version 1.3.1

Horde>>Horde_application_framework >> Version 1.3.2

Horde>>Horde_application_framework >> Version 1.3.3

Horde>>Horde_application_framework >> Version 1.3.4

Horde>>Horde_application_framework >> Version 1.3.5

Horde>>Horde_application_framework >> Version 2.0

Horde>>Horde_application_framework >> Version 2.0

Horde>>Horde_application_framework >> Version 2.0

Horde>>Horde_application_framework >> Version 2.0

Horde>>Horde_application_framework >> Version 2.1

Horde>>Horde_application_framework >> Version 2.2

Horde>>Horde_application_framework >> Version 2.2.1

Horde>>Horde_application_framework >> Version 2.2.2

Horde>>Horde_application_framework >> Version 2.2.3

Horde>>Horde_application_framework >> Version 2.2.4

Horde>>Horde_application_framework >> Version 2.2.5

Horde>>Horde_application_framework >> Version 2.2.6

Horde>>Horde_application_framework >> Version 2.2.6

Horde>>Horde_application_framework >> Version 2.2.7

Horde>>Horde_application_framework >> Version 2.2.8

Horde>>Horde_application_framework >> Version 2.2.9

Horde>>Horde_application_framework >> Version 3.0

Horde>>Horde_application_framework >> Version 3.0

Horde>>Horde_application_framework >> Version 3.0

Horde>>Horde_application_framework >> Version 3.0

Horde>>Horde_application_framework >> Version 3.0

Horde>>Horde_application_framework >> Version 3.0

Horde>>Horde_application_framework >> Version 3.0.1

Horde>>Horde_application_framework >> Version 3.0.2

Horde>>Horde_application_framework >> Version 3.0.3

Horde>>Horde_application_framework >> Version 3.0.3

Horde>>Horde_application_framework >> Version 3.0.4

Horde>>Horde_application_framework >> Version 3.0.4

Horde>>Horde_application_framework >> Version 3.0.4

Horde>>Horde_application_framework >> Version 3.0.5

Horde>>Horde_application_framework >> Version 3.0.5

Horde>>Horde_application_framework >> Version 3.0.5

Horde>>Horde_application_framework >> Version 3.0.6

Horde>>Horde_application_framework >> Version 3.0.6

Horde>>Horde_application_framework >> Version 3.0.7

Horde>>Horde_application_framework >> Version 3.0.8

Horde>>Horde_application_framework >> Version 3.0.9

Horde>>Horde_application_framework >> Version 3.0.10

Horde>>Horde_application_framework >> Version 3.0.11

Horde>>Horde_application_framework >> Version 3.0.12

Horde>>Horde_application_framework >> Version 3.1

Horde>>Horde_application_framework >> Version 3.1

Horde>>Horde_application_framework >> Version 3.1

Horde>>Horde_application_framework >> Version 3.1

Horde>>Horde_application_framework >> Version 3.1.1

Horde>>Horde_application_framework >> Version 3.1.2

Horde>>Horde_application_framework >> Version 3.1.3

Horde>>Horde_application_framework >> Version 3.1.4

Horde>>Horde_application_framework >> Version 3.1.4

Horde>>Horde_application_framework >> Version 3.1.5

Horde>>Horde_application_framework >> Version 3.1.6

Horde>>Horde_application_framework >> Version 3.1.7

Horde>>Horde_application_framework >> Version 3.1.8

Horde>>Horde_application_framework >> Version 3.1.9

Horde>>Horde_application_framework >> Version 3.2

Horde>>Horde_application_framework >> Version 3.2

Horde>>Horde_application_framework >> Version 3.2

Horde>>Horde_application_framework >> Version 3.2

Horde>>Horde_application_framework >> Version 3.2

Horde>>Horde_application_framework >> Version 3.2

Horde>>Horde_application_framework >> Version 3.2.1

Horde>>Horde_application_framework >> Version 3.2.2

Horde>>Horde_application_framework >> Version 3.2.3

Horde>>Horde_application_framework >> Version 3.2.4

Horde>>Horde_application_framework >> Version 3.2.5

Horde>>Horde_application_framework >> Version 3.3

Horde>>Horde_application_framework >> Version 3.3

Horde>>Horde_application_framework >> Version 3.3.1

Horde>>Horde_application_framework >> Version 3.3.2

Horde>>Horde_application_framework >> Version 3.3.3

Horde>>Horde_application_framework >> Version 3.3.4

Horde>>Horde_application_framework >> Version 3.3.4

Horde>>Horde_application_framework >> Version 3.3.5

Horde>>Horde_application_framework >> Version 3.3.6

Horde>>Horde_application_framework >> Version 3.3.7

References

http://secunia.com/advisories/42140
Tags : third-party-advisory, x_refsource_SECUNIA