-
Notifications
You must be signed in to change notification settings - Fork 0
/
info-disclosure2.txt
356 lines (311 loc) · 20.8 KB
/
info-disclosure2.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
# updated webtask, new gathering info
cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support/"
BUG_REPORT_URL="https://bugs.debian.org/"
env
CLUSTER_SIZE=1
NODE_VERSION=0.12.6
HOSTNAME=529f54d98807
GET_CODE_TIMEOUT=10000
SHLVL=1
HOME=/
PORT=/data/io/port.sock
OLDPWD=/data/io
EDGE_CS_TEMP_DIR=/data/io
_=/etc/os-release
VERQUIRE_DIR=/data/_verquire
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
SANDBOX_STATS_HEADER=1
NPM_VERSION=2.11.3
MAX_CODE_SIZE=100
TRIPWIRE_TIMEOUT_MS=2000
COOLDOWN_TIMEOUT=1000
BACKCHANNEL_PORT=/data/backchannel.sock
EDGE_CS_CACHE=1
MAX_CODE_CACHE_COUNT=10
PWD=/data
OS_LIMITS=nproc=100:100,nofile=2048:2048
December Security Release Summary
by Rod Vagg, 2015-12-04
Last week we announced the planned release of patch updates to the v0.12.x, v4.x and v5.x lines to fix two vulnerabilities. That was further amended by the announcement of OpenSSL updates with fixes for vulnerabilities labelled medium severity. The OpenSSL update impacts all active release lines, including v0.10.x.
Today we have released Node.js v0.10.41 (Maintenance), v0.12.9 (LTS), v4.2.3 "Argon" (LTS) and v5.1.1 (Stable) with fixes for the announced vulnerabilities and updates to OpenSSL.
For the purpose of understanding the impact that the fixed vulnerabilities have on your Node.js deployment and the urgency of the upgrades for your circumstances we are providing details below.
CVE-2015-8027 Denial of Service Vulnerability
This critical denial of service (DoS) vulnerability impacts all versions of v0.12.x through to v5.x, inclusive. The vulnerability was discovered by Node.js core team member Fedor Indutny and relates to HTTP pipelining. Under certain conditions an HTTP socket may no longer have a parser associated with it but a pipelined request can trigger a pause or resume on the non-existent parser thereby causing an uncaughtException to be thrown. As these conditions can be created by an external attacker and cause a Node.js service to be shut down we consider this a critical vulnerability. It is recommended that users of impacted versions of Node.js exposing HTTP services upgrade to the appropriate patched versions as soon as practical.
Versions 0.10.x of Node.js are not affected.
Versions 0.12.x of Node.js are vulnerable, please upgrade to v0.12.9 (LTS).
Versions 4.x, including LTS Argon, of Node.js are vulnerable, please upgrade to v4.2.3 "Argon" (LTS).
Versions 5.x of Node.js are vulnerable, please upgrade to v5.1.1 (Stable).
CVE-2015-6764 V8 Out-of-bounds Access Vulnerability
A bug was discovered in V8's implementation of JSON.stringify() that can result in out-of-bounds reads on arrays. The patch was included in this week's update of Chrome Stable. While this bug is high severity for browsers, it is considered lower risk for Node.js users as it requires the execution of third-party JavaScript within an application in order to be exploitable.
Node.js users who expose services that process untrusted user-supplied JavaScript are at obvious risk. However, we recommend that all users of impacted versions of Node.js upgrade to the appropriate patched version in order to protect against malicious third-party JavaScript that may be executed within a Node.js process by other means.
Versions 0.10.x of Node.js are not affected.
Versions 0.12.x of Node.js are not affected.
Versions 4.x, including LTS Argon, of Node.js are vulnerable, please upgrade to v4.2.3 "Argon" (LTS).
Versions 5.x of Node.js are vulnerable, please upgrade to v5.1.1 (Stable).
CVE-2015-3193 OpenSSL BN_mod_exp may produce incorrect results on x86_64
A bug exists in OpenSSL v1.0.2 in the Montgomery squaring procedure on the x64 architecture that expose potential attack vectors. Attacks against RSA and DSA are considered possible but with a very high degree of difficulty. Attacks against DHE key exchange is considered feasible but difficult. EC algorithms are not vulnerable. Node.js TLS servers using DHE key exchange are considered at highest risk although it is believed that Node.js' existing use of SSL_OP_SINGLE_DH_USE may make DHE attacks impractical. Details are available at http://openssl.org/news/secadv/20151203.txt.
OpenSSL v1.0.2 is used in Node.js v4.x LTS and v5.x. It is strongly recommended that Node.js users exposing TLS servers upgrade to patched versions as soon as practical.
Versions 0.10.x of Node.js are not affected.
Versions 0.12.x of Node.js are not affected.
Versions 4.x, including LTS Argon, of Node.js are vulnerable, please upgrade to v4.2.3 "Argon" (LTS).
Versions 5.x of Node.js are vulnerable, please upgrade to v5.1.1 (Stable).
CVE-2015-3194 OpenSSL Certificate verify crash with missing PSS parameter
A bug exists in OpenSSL v1.0.1 and v1.0.2 that may cause a crash during certificate verification procedures when supplied with a malformed ASN.1 signature using the RSA PSS algorithm. This may be used as a the basis of a denial of service (DoS) attack against Node.js TLS servers using client authentication. Node.js TLS clients are also impacted if supplied with malformed certificates for verification. Details are available at http://openssl.org/news/secadv/20151203.txt.
OpenSSL v1.0.0 is used in Node.js v0.10.x and v0.12.x. OpenSSL v1.0.2 is used in Node.js v4.x LTS and v5.x. It is strongly recommended that Node.js users employing either TLS client or server code upgrade as soon as practical.
Versions 0.10.x of Node.js are vulnerable, please upgrade to v0.10.41 (Maintenance).
Versions 0.12.x of Node.js are vulnerable, please upgrade to v0.12.9 (LTS).
Versions 4.x, including LTS Argon, of Node.js are vulnerable, please upgrade to v4.2.3 "Argon" (LTS).
Versions 5.x of Node.js are vulnerable, please upgrade to v5.1.1 (Stable).
Note: Node.js users are not considered vulnerable to the two additional announced OpenSSL vulnerabilities: CVE-2015-3195 "X509_ATTRIBUTE memory leak" and CVE-2015-3196 "Race condition handling PSK identify hint". However, fixes for these bugs are included with the new versions of OpenSSL bundled with the newly patched versions of Node.js.
Starting Nmap 7.01 ( https://nmap.org ) at 2016-01-16 13:42 UTC
Unable to find nmap-services! Resorting to /etc/services
Cannot find nmap-payloads. UDP payloads are disabled.
Nmap scan report for ec2-107-20-188-61.compute-1.amazonaws.com (107.20.188.61)
Host is up (0.069s latency).
Not shown: 65533 filtered ports
PORT STATE SERVICE
22/tcp open ssh
8721/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 429.98 seconds
Starting Nmap 7.01 ( https://nmap.org ) at 2016-01-16 14:06 UTC
Unable to find nmap-services! Resorting to /etc/services
Cannot find nmap-payloads. UDP payloads are disabled.
Nmap scan report for ec2-177-71-160-151.sa-east-1.compute.amazonaws.com (177.71.160.151) ##dev.auth0.com cert
Host is up (0.19s latency).
Not shown: 65530 filtered ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
443/tcp open https
5672/tcp open amqp
27017/tcp open unknown ##mongodb! 2.6.11 requires auth
Nmap done: 1 IP address (1 host up) scanned in 249.52 seconds
Starting Nmap 7.01 ( https://nmap.org ) at 2016-01-16 14:12 UTC
Unable to find nmap-services! Resorting to /etc/services
Cannot find nmap-payloads. UDP payloads are disabled.
Nmap scan report for ec2-52-16-142-128.eu-west-1.compute.amazonaws.com (52.16.142.128)
Host is up (0.14s latency).
Not shown: 65534 filtered ports
PORT STATE SERVICE
22/tcp open ssh
Nmap done: 1 IP address (1 host up) scanned in 325.78 seconds
Starting Nmap 7.01 ( https://nmap.org ) at 2016-01-16 14:59 UTC
Unable to find nmap-services! Resorting to /etc/services
Cannot find nmap-payloads. UDP payloads are disabled.
Nmap scan report for ec2-52-8-12-98.us-west-1.compute.amazonaws.com (52.8.12.98)
Host is up (0.0011s latency).
Not shown: 65533 filtered ports
PORT STATE SERVICE
443/tcp open https
943/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 202.00 seconds
Starting Nmap 7.01 ( https://nmap.org ) at 2016-01-16 15:05 UTC
Unable to find nmap-services! Resorting to /etc/services
Cannot find nmap-payloads. UDP payloads are disabled.
Nmap scan report for ec2-54-193-6-52.us-west-1.compute.amazonaws.com (54.193.6.52)
Host is up (0.00093s latency).
Not shown: 65532 filtered ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp closed http
443/tcp closed https
Nmap done: 1 IP address (1 host up) scanned in 202.71 seconds
Starting Nmap 7.01 ( https://nmap.org ) at 2016-01-16 15:32 UTC
Unable to find nmap-services! Resorting to /etc/services
Initiating Parallel DNS resolution of 1 host. at 15:32
Completed Parallel DNS resolution of 1 host. at 15:32, 0.01s elapsed
Cannot find nmap-payloads. UDP payloads are disabled.
Initiating Connect Scan at 15:32
Scanning ec2-54-94-200-76.sa-east-1.compute.amazonaws.com (54.94.200.76) [65535 ports]
Discovered open port 22/tcp on 54.94.200.76
Discovered open port 80/tcp on 54.94.200.76
Discovered open port 443/tcp on 54.94.200.76
Connect Scan Timing: About 7.34% done; ETC: 15:39 (0:06:31 remaining)
Connect Scan Timing: About 19.44% done; ETC: 15:37 (0:04:13 remaining)
Connect Scan Timing: About 34.39% done; ETC: 15:36 (0:02:54 remaining)
Connect Scan Timing: About 47.66% done; ETC: 15:36 (0:02:13 remaining)
Connect Scan Timing: About 60.36% done; ETC: 15:37 (0:01:57 remaining)
Connect Scan Timing: About 69.95% done; ETC: 15:37 (0:01:29 remaining)
Connect Scan Timing: About 80.31% done; ETC: 15:38 (0:01:11 remaining)
Connect Scan Timing: About 86.31% done; ETC: 15:38 (0:00:52 remaining)
Connect Scan Timing: About 92.12% done; ETC: 15:38 (0:00:32 remaining)
Completed Connect Scan at 15:39, 426.95s elapsed (65535 total ports)
Nmap scan report for ec2-54-94-200-76.sa-east-1.compute.amazonaws.com (54.94.200.76)
Host is up, received user-set (0.19s latency).
Scanned at 2016-01-16 15:32:07 UTC for 427s
Not shown: 65532 filtered ports
Reason: 65532 no-responses
PORT STATE SERVICE REASON
22/tcp open ssh syn-ack
80/tcp open http syn-ack
443/tcp open https syn-ack
Read data files from: /etc
Nmap done: 1 IP address (1 host up) scanned in 426.96 seconds
Starting Nmap 7.01 ( https://nmap.org ) at 2016-01-16 15:33 UTC
Unable to find nmap-services! Resorting to /etc/services
Initiating Parallel DNS resolution of 1 host. at 15:33
Completed Parallel DNS resolution of 1 host. at 15:33, 0.00s elapsed
Cannot find nmap-payloads. UDP payloads are disabled.
Initiating Connect Scan at 15:33
Scanning ec2-54-183-204-205.us-west-1.compute.amazonaws.com (54.183.204.205) [65535 ports]
Discovered open port 22/tcp on 54.183.204.205
Connect Scan Timing: About 7.11% done; ETC: 15:41 (0:06:45 remaining)
Increasing send delay for 54.183.204.205 from 0 to 5 due to 11 out of 29 dropped probes since last increase.
Connect Scan Timing: About 12.29% done; ETC: 15:42 (0:07:15 remaining)
Connect Scan Timing: About 30.97% done; ETC: 15:43 (0:06:50 remaining)
Connect Scan Timing: About 37.35% done; ETC: 15:43 (0:06:19 remaining)
Connect Scan Timing: About 43.27% done; ETC: 15:44 (0:05:47 remaining)
Connect Scan Timing: About 49.19% done; ETC: 15:44 (0:05:14 remaining)
Connect Scan Timing: About 54.66% done; ETC: 15:44 (0:04:42 remaining)
Connect Scan Timing: About 60.13% done; ETC: 15:44 (0:04:09 remaining)
Connect Scan Timing: About 65.60% done; ETC: 15:44 (0:03:36 remaining)
Connect Scan Timing: About 71.05% done; ETC: 15:44 (0:03:03 remaining)
Connect Scan Timing: About 76.06% done; ETC: 15:44 (0:02:31 remaining)
Connect Scan Timing: About 81.50% done; ETC: 15:44 (0:01:57 remaining)
Connect Scan Timing: About 87.62% done; ETC: 15:45 (0:01:24 remaining)
Connect Scan Timing: About 93.42% done; ETC: 15:45 (0:00:48 remaining)
Completed Connect Scan at 15:46, 748.93s elapsed (65535 total ports)
Nmap scan report for ec2-54-183-204-205.us-west-1.compute.amazonaws.com (54.183.204.205)
Host is up, received user-set (0.0016s latency).
Scanned at 2016-01-16 15:33:51 UTC for 749s
Not shown: 65534 filtered ports
Reason: 65534 no-responses
PORT STATE SERVICE REASON
22/tcp open ssh syn-ack
Read data files from: /etc
Nmap done: 1 IP address (1 host up) scanned in 748.94 seconds
Starting Nmap 7.01 ( https://nmap.org ) at 2016-01-16 15:33 UTC
Unable to find nmap-services! Resorting to /etc/services
Initiating Parallel DNS resolution of 1 host. at 15:33
Completed Parallel DNS resolution of 1 host. at 15:33, 0.00s elapsed
Cannot find nmap-payloads. UDP payloads are disabled.
Initiating Connect Scan at 15:33
Scanning ec2-54-183-204-205.us-west-1.compute.amazonaws.com (54.183.204.205) [65535 ports]
Discovered open port 22/tcp on 54.183.204.205
Connect Scan Timing: About 7.11% done; ETC: 15:41 (0:06:45 remaining)
Increasing send delay for 54.183.204.205 from 0 to 5 due to 11 out of 29 dropped probes since last increase.
Connect Scan Timing: About 12.29% done; ETC: 15:42 (0:07:15 remaining)
Connect Scan Timing: About 30.97% done; ETC: 15:43 (0:06:50 remaining)
Connect Scan Timing: About 37.35% done; ETC: 15:43 (0:06:19 remaining)
Connect Scan Timing: About 43.27% done; ETC: 15:44 (0:05:47 remaining)
Connect Scan Timing: About 49.19% done; ETC: 15:44 (0:05:14 remaining)
Connect Scan Timing: About 54.66% done; ETC: 15:44 (0:04:42 remaining)
Connect Scan Timing: About 60.13% done; ETC: 15:44 (0:04:09 remaining)
Connect Scan Timing: About 65.60% done; ETC: 15:44 (0:03:36 remaining)
Connect Scan Timing: About 71.05% done; ETC: 15:44 (0:03:03 remaining)
Connect Scan Timing: About 76.06% done; ETC: 15:44 (0:02:31 remaining)
Connect Scan Timing: About 81.50% done; ETC: 15:44 (0:01:57 remaining)
Connect Scan Timing: About 87.62% done; ETC: 15:45 (0:01:24 remaining)
Connect Scan Timing: About 93.42% done; ETC: 15:45 (0:00:48 remaining)
Completed Connect Scan at 15:46, 748.93s elapsed (65535 total ports)
Nmap scan report for ec2-54-183-204-205.us-west-1.compute.amazonaws.com (54.183.204.205)
Host is up, received user-set (0.0016s latency).
Scanned at 2016-01-16 15:33:51 UTC for 749s
Not shown: 65534 filtered ports
Reason: 65534 no-responses
PORT STATE SERVICE REASON
22/tcp open ssh syn-ack
Read data files from: /etc
Nmap done: 1 IP address (1 host up) scanned in 748.94 seconds
find / -type f -perm -o+w -exec ls -alh {} \;
find: `/etc/ssl/private': Permission denied
-rw-rw-rw- 1 root root 0 Jan 16 15:54 /proc/sys/kernel/ns_last_pid
find: `/proc/tty/driver': Permission denied
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/1/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/1/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/1/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/1/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/1/attr/sockcreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/6/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/6/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/6/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/6/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/6/attr/sockcreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/7/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/7/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/7/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/7/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/7/attr/sockcreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/8/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/8/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/8/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/8/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/8/attr/sockcreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/9/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/9/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/9/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/9/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/9/attr/sockcreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/10/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/10/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/10/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/10/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/10/attr/sockcreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/11/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/11/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/11/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/11/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/11/attr/sockcreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/12/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/12/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/12/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/12/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/12/attr/sockcreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/13/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/13/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/13/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/13/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/13/attr/sockcreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/14/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/14/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/14/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/14/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/task/14/attr/sockcreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/1/attr/sockcreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/21/task/21/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/21/task/21/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/21/task/21/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/21/task/21/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/21/task/21/attr/sockcreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/21/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/21/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/21/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/21/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/21/attr/sockcreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/22/task/22/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/22/task/22/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/22/task/22/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/22/task/22/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/22/task/22/attr/sockcreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/22/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/22/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/22/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/22/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/22/attr/sockcreate
find: `/proc/27/task/27/fd/6': No such file or directory
find: `/proc/27/task/27/fdinfo/6': No such file or directory
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/27/task/27/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/27/task/27/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/27/task/27/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/27/task/27/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/27/task/27/attr/sockcreate
find: `/proc/27/fd/6': No such file or directory
find: `/proc/27/fdinfo/6': No such file or directory
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/27/attr/current
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/27/attr/exec
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/27/attr/fscreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/27/attr/keycreate
-rw-rw-rw- 1 30025 root 0 Jan 16 15:54 /proc/27/attr/sockcreate
find: `/root': Permission denied
find: `/var/cache/ldconfig': Permission denied