Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

A8: Angular instead of AngularJS (A8) #5

Closed
binarious opened this issue Apr 25, 2017 · 1 comment
Closed

A8: Angular instead of AngularJS (A8) #5

binarious opened this issue Apr 25, 2017 · 1 comment
Assignees
@infosecdad
Labels
A8 bug
Milestone
RC2

Comments

@binarious
Copy link

In A8 in the section How Do I Prevent CSRF you wrote:

[...] such as Spring, Play, Django, and AngularJS.

You're linking to the Docs of the new Angular version which is just called Angular. AngularJS is version 1.x.
@sslHello sslHello changed the title Angular instead of AngularJS (A8) A8: Angular instead of AngularJS (A8) Jun 17, 2017
@sslHello sslHello mentioned this issue Jun 17, 2017
Closed
@vanderaj vanderaj added this to the RC2 milestone Sep 23, 2017
sslHello added a commit that referenced this issue Sep 30, 2017
@sslHello
Example Scenarios: added 'Scenario #5' (default/old configuration)
8058cea 
Added 'Scenario #5: The default configuration or a copied old one activates old vulnerable protocol versions or options that can be misused by an attacker or malware.'
@vanderaj
Copy link
Member

CSRF is out, so closing tickets.

@sslHello sslHello mentioned this issue Oct 16, 2017
Closed
sslHello added a commit that referenced this issue Oct 16, 2017
@sslHello
I've done the last 2 of #136 before I handle it over to Andrew
84b30dc 
see #136:
@ossie-git thank you for your various comments
I've done the last 2 before I handle it over to Andrew:

    effectiveness, -> OK
    Are any administration interfaces exposed to users? added (I do appreciate this, it's one of my favorites for this issue ;-) ) But I am sorry, there was no space left for the examples ' (application, application server, etc.)'

@vanderaj But we need to economize 2 lines in the box with 'Example Attack Scenarios' (to get some space for Scenario #5)

    Added the Links from RC1

Thank you.
Cheers Torsten
@sumitagarwalusa sumitagarwalusa mentioned this issue Oct 23, 2017
Closed
sslHello pushed a commit that referenced this issue May 24, 2018
@adeyosemanputra
Merge pull request #5 from MangatasTondang/patch-4
5b9dd16 
Update 0xd0-about-data.md
sslHello pushed a commit that referenced this issue Feb 25, 2019
@pontocom
Merge pull request #5 from PauloASilva/review
fb6c3a7 
review "Foreward"
@infosecdad infosecdad mentioned this issue Sep 18, 2021
Closed
sslHello pushed a commit that referenced this issue Sep 21, 2021
@ninedter
Merge pull request #5 from htchen99/2021-zhtw
77834be 
2021 zhtw
sslHello pushed a commit that referenced this issue Sep 21, 2021
@okdt
Merge pull request #5 from springmoon6/master
d78a7e8 
Update A06_2021-Vulnerable_and_Outdated_Components.ja.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@infosecdad infosecdad

Labels
A8 bug
Projects
None yet
Milestone
RC2
Development

No branches or pull requests
4 participants
@binarious @Neil-Smithline @vanderaj @infosecdad