Lucene search
+L

547 matches found

exploitpack
exploitpack
added 2010/01/30 12:0 a.m.13 views

dotProject 2.1.3 - Cross-Site Scripting Improper Permissions

dotProject 2.1.3 - Cross-Site Scripting Improper Permissions Exploit Title: dotProject 2.1.3 XSS and Improper Permissions Date: Dec 15 2009 Author: h00die [email protected] & S0lus Software Link:...

0.5AI score
SaveExploits0
zdt
zdt
added 2010/01/30 12:0 a.m.26 views

dotProject 2.1.3 XSS and Improper Permissions

Exploit for unknown platform in category web applications ============================================= dotProject 2.1.3 XSS and Improper Permissions ============================================= Exploit Title: dotProject 2.1.3 XSS and Improper Permissions Date: Dec 15 2009 Author: h00die Softwar...

7.1AI score
SaveExploits0
Exploit DB
Exploit DB
added 2010/01/30 12:0 a.m.28 views

dotProject 2.1.3 - Cross-Site Scripting / Improper Permissions

Exploit Title: dotProject 2.1.3 XSS and Improper Permissions Date: Dec 15 2009 Author: h00die [email protected] & S0lus Software Link: http://sourceforge.net/projects/dotproject/files/dotproject/dotProject%20Version%202.1.3/dotproject213.zip/download Version: 2.1.3 Tested on: BT4 pre-final Greetz to...

5.8AI score
SaveExploits0
Tenable Nessus
Tenable Nessus
added 2009/09/16 12:0 a.m.8 views

Best Practical Request Tracker 'Custom Field' HTML Injection Vulnerability

Binary data 5177.prm...

7.3AI score
SaveExploits0References1
Atlassian
Atlassian
added 2009/09/02 3:54 p.m.35 views

"User Custom Field Value" permission type incorrectly exposes JIRA project names to everyone

Problem: Project names are shown to users with no permission to see the project. Impact: Security hole! Recipe: it helps to have two browsers open one logged in as admin the other as the user I will create called dummy Add user dummy Add project blah Add custom field myuser of type user picker,...

6.8AI score
SaveExploits0Affected Software1
Atlassian
Atlassian
added 2009/09/02 3:54 p.m.21 views

"User Custom Field Value" permission type incorrectly exposes JIRA project names to everyone

Problem: Project names are shown to users with no permission to see the project. Impact: Security hole! Recipe: it helps to have two browsers open one logged in as admin the other as the user I will create called dummy Add user dummy Add project blah Add custom field myuser of type user picker,...

6.8AI score
SaveExploits0Affected Software1
Atlassian
Atlassian
added 2009/07/28 5:51 a.m.29 views

Allow issue security level to use any custom field that implements UserCFNotificationTypeAware

It would be useful to be able to set the security level on an issue to include everyone who participated on an issue so if you had a security level that was only the reporter and the assignee, if the issue needs to get reassigned the issue could still be seen by the original assignee. The JIRA...

0.6AI score
SaveExploits0Affected Software1
Atlassian
Atlassian
added 2009/07/28 5:51 a.m.32 views

Allow issue security level to use any custom field that implements UserCFNotificationTypeAware

panel:bgColor=e7f4fa NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-18099. panel It would be useful to be able to set the security level on an issue to include everyone who participated on an issue so if you h...

0.8AI score
SaveExploits0Affected Software1
Atlassian
Atlassian
added 2009/07/28 5:51 a.m.26 views

Allow issue security level to use any custom field that implements UserCFNotificationTypeAware

panel:bgColor=e7f4fa NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-18099. panel It would be useful to be able to set the security level on an issue to include everyone who participated on an issue so if you...

0.8AI score
SaveExploits0Affected Software1
Prion
Prion
added 2008/01/17 10:0 p.m.18 views

Cross site scripting

Cross-site scripting XSS vulnerability in BugTracker.NET before 2.7.2 allows remote attackers to inject arbitrary web script or HTML via an arbitrary custom text field...

4.3CVSS6.1AI score0.01065EPSS
SaveExploits0References5Affected Software1
Atlassian
Atlassian
added 2007/11/02 3:23 a.m.23 views

You are able to delete a Custom Field that is referenced in Permission settings.

If you add a User Custom Field as a permission in a permission scheme or issue level security scheme, you are then able to delete the Custom Field without validation or warnings. After deleting the field, you are still able to see the Custom Field ID in the permission scheme, although it can...

1AI score
SaveExploits0Affected Software1
Atlassian
Atlassian
added 2007/11/02 3:23 a.m.24 views

You are able to delete a Custom Field that is referenced in Permission settings.

If you add a User Custom Field as a permission in a permission scheme or issue level security scheme, you are then able to delete the Custom Field without validation or warnings. After deleting the field, you are still able to see the Custom Field ID in the permission scheme, although it can...

1AI score
SaveExploits0Affected Software1
Atlassian
Atlassian
added 2007/11/02 3:23 a.m.26 views

You are able to delete a Custom Field that is referenced in Permission settings.

If you add a User Custom Field as a permission in a permission scheme or issue level security scheme, you are then able to delete the Custom Field without validation or warnings. After deleting the field, you are still able to see the Custom Field ID in the permission scheme, although it can...

1AI score
SaveExploits0
Atlassian
Atlassian
added 2007/10/24 6:4 a.m.22 views

Issues not shown in issue navigator that a user has permission for according to the issue security level

Users may not be able to see certain issues in the IssueNavigator, if they create an issue level security, where the permission depends on a user custom field where the customfield does not have a searcher set. Browsing the issue directly, works fine, however when running a search the issue wont ...

0.8AI score
SaveExploits0Affected Software1
Atlassian
Atlassian
added 2007/10/24 6:4 a.m.29 views

Issues not shown in issue navigator that a user has permission for according to the issue security level

Users may not be able to see certain issues in the IssueNavigator, if they create an issue level security, where the permission depends on a user custom field where the customfield does not have a searcher set. Browsing the issue directly, works fine, however when running a search the issue wont ...

0.8AI score
SaveExploits0Affected Software1
Atlassian
Atlassian
added 2007/10/24 6:4 a.m.21 views

Issues not shown in issue navigator that a user has permission for according to the issue security level

Users may not be able to see certain issues in the IssueNavigator, if they create an issue level security, where the permission depends on a user custom field where the customfield does not have a searcher set. Browsing the issue directly, works fine, however when running a search the issue wont ...

0.8AI score
SaveExploits0
Atlassian
Atlassian
added 2007/10/09 3:24 p.m.26 views

user value of JiraAuthenticationContext not set is SOAP service getIssue()

Call to JiraAuthenticationContext.setUser missing during getIssue SOAP service call. Service call will fail silently if there are custom fields with explicit secutity checking for attributes derived from current user. In my case I try to verify existance of an issue using getIssue SOAP service...

1.6AI score
SaveExploits0
Atlassian
Atlassian
added 2007/09/13 5:12 a.m.17 views

Multi user custom field cannot be used with the assignable user permission

If a multi user custom field is added to JIRA, and the custom field is added to the Assignable User permission, the Assign Issue operation breaks, when trying to gather the list of assignable Users. This is basically because our MultiUserCF is not specific enough and relies to much on the...

0.4AI score
SaveExploits0Affected Software1
Atlassian
Atlassian
added 2007/09/13 5:12 a.m.58 views

Multi user custom field cannot be used with the assignable user permission

If a multi user custom field is added to JIRA, and the custom field is added to the Assignable User permission, the Assign Issue operation breaks, when trying to gather the list of assignable Users. This is basically because our MultiUserCF is not specific enough and relies to much on the...

0.4AI score
SaveExploits0Affected Software1
Atlassian
Atlassian
added 2007/09/13 5:12 a.m.19 views

Multi user custom field cannot be used with the assignable user permission

If a multi user custom field is added to JIRA, and the custom field is added to the Assignable User permission, the Assign Issue operation breaks, when trying to gather the list of assignable Users. This is basically because our MultiUserCF is not specific enough and relies to much on the...

0.4AI score
SaveExploits0
Rows per page
Query Builder