[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <201312120501.rBC51RVC026250@linus.mitre.org>
Date: Thu, 12 Dec 2013 00:01:27 -0500 (EST)
From: cve-assign@...re.org
To: henri@...v.fi
Cc: cve-assign@...re.org, oss-security@...ts.openwall.com
Subject: Re: CVE request: TYPO3-CORE-SA-2013-004 and TYPO3-FLOW-SA-2013-001
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
For the issues that were numbered 1-10 in your message:
1) CVE-2013-7073
2) CVE-2013-7074
3) CVE-2013-7075
4) CVE-2013-7076
5) CVE-2013-7077
6) CVE-2013-7078
7) CVE-2013-7079
8) CVE-2013-7080
9) CVE-2013-7081
10) CVE-2013-7082
Also, for issue 3, are you disclosing a CSRF vulnerability? Or are you
just saying that, theoretically, if a CSRF vulnerability existed, that
would be one way to conduct the attack?
We'll assign another CVE ID if CSRF is being disclosed here.
- --
CVE assignment team, MITRE CVE Numbering Authority
M/S M300
202 Burlington Road, Bedford, MA 01730 USA
[ PGP key available through http://cve.mitre.org/cve/request_id.html ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (SunOS)
iQEcBAEBAgAGBQJSqULiAAoJEKllVAevmvmsYY0H/REu+zTywg4aZvUJWF5QSXLT
5iPAUgal7JQWBKW7g5H6UKkoZ/WoDqyqlZ4Jtut39B4luu82OLEBArmEyA2VoSWZ
r42u53fQH1OmLv/mDumHpIQ3Of42AjNVsafE2+5gqSumi+e1neIDMCYyV0mfvwG8
+9VLO/Y9wh91srA7ZLmXMU4it15RM6z4CAcNQjQGS+ylIOx3M5grIC8uRCoYqKP4
sVz8CNMIR65+X2Q7Aaw42b5IyRRpb0qwMFL46ScJWFJGQUdO08I3n4YBaMQOz0Yl
vKOG43sE2vNK3kq9f0zT2U5vYINIafXYadw0mpi79AVIirS5xeSqLyMpJUkneGs=
=luW2
-----END PGP SIGNATURE-----
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
