2024FIC竞赛

密码

2024Fic@杭州Powered~by~HL!

手机部分

1.嫌疑人李某的手机型号是?

A. Xiaomi MI 2s
B. Xiaomi MI 4
C. Xiaomi MI 6
D. Xiaomi MI 8

取证软件无法解析,需要自行从文件目录中搜索,

Xiaomi_2403181352-1710731652.img/1/misc/location/xtra/useragent.txt

image-20240430171945603

B

2.嫌疑人李某是否可能有平板电脑设备,该设备型号是?

A. iPad Pro 11
B. Vivo Pad2
C. MatePad Pro
D. Xiaomi Pad 6s

image-20240429175242115

D

3.嫌疑人李某手机开启热点设置的密码是?

image-20240429175400504

5aada11bc1b5

4.嫌疑人李某的微信内部ID是?

image-20240429175416175

wxid_wnigmud8aj6j12

5.嫌疑人李某发送给技术人员的网站源码下载地址是什么

image-20240429175600937

image-20240429180753255

新佛曰:諸隸僧殿降吽諸陀摩隸殿僧殿缽殿薩願僧殿宣摩殿嚴願殿是迦咒叻吶嚤須塞亦須阿隸嚤須愍眾殿蜜殿隸願蜜哆蜜亦願是念慧殿隸摩哆殿即隸嚤訶須隸亦愍如如殿囑殿囑

http://hi.pcmoe.net/buddha.html

image-20240429181036213

http://www.honglian7001.com/down

6.受害者微信用户ID是?

image-20240429175815651

image-20240429175838325

limoon890

7.嫌疑人李某第一次连接WIFI的时间是?

A.03-14 15:55:57
B.03-14 16:55:57
C.03-14 17:55:57
D.03-14 18:55:57

image-20240429180423910

B

8.分析嫌疑人李某的社交习惯,哪一段时间消息收发最活跃?

A.12:00-14:00
B.14:00-16:00
C.16:00-18:00
D.18:00-20:00

分析可得

C

9.请分析嫌疑人手机,该案件团伙中,还有一名重要参与者警方未抓获,该嫌疑人所使用的微信账号ID为?

老苏是重要参与者

image-20240429180224625

wxid_kolc5oaiap6z22

10.请分析嫌疑人手机、嫌疑人老板组织人员参与博彩活动、所使用的国内访问入口地址为1

image-20240429181311373

192.168.110.110:8000/login

服务器供应问题

*虚拟机配置

image-20240429201212990

image-20240429201510507

*手动挂载

手动绕密看似更难,却可以实现百分百仿真,因为虚拟机设置可能存在开机自启等选项

首先使用FTK挂载ESXI的镜像。(此处注意点:挂载选项选择“物理”和“逻辑”;注意选择“逻辑”挂载是因为需要进入分区修改shadow文件)

image-20240506084623568

打开FTK挂载出来的虚拟磁盘,在250MB大小的一个分区找到state.gz文件。

image-20240506084122235

image-20240506084152251

有了etc目录,绕密方式就比较明显了,将/etc/shadow文件root密码置空,重新按照路径选择tar.gz压缩回去后替换原文件。

image-20240506084351488

替换后完成后,使用VMware选择“创建新的虚拟机”,使用FTK挂载的物理磁盘,创建完成之后,即可启动新的虚拟机,ESXi密码此时已被清除,可以直接空密码登录。

由于是集群仿真,在仿真时需要勾选cpu嵌套虚拟化功能“Intel VT-x/AMD-V”,否则无法在虚拟机中再开虚拟机

一开始选择自定义选项

image-20240506090457775 image-20240506090538793 image-20240506085608812

根据FTK选择对应的物理磁盘

image-20240506085759829 image-20240506090127884

仿真成功

1.esxi服务器的esxi版本是什么?

image-20240429182236168

6.7.0

2.请分析ESXi服务器,该系统的安装日期为:

A.2024年3月12日星期二02:04:15UTC
B.2024年3月12日星期二02:05:15UTC
C.2024年3月12日星期二02:06:15UTC
D.2024年3月12日星期二02:07:15UTC

image-20240429182640201

D

3.请分析ESXi服务器数据存储“datastore”的UUID是?

image-20240429182348867

65efb8a8-ddd817f6-04ff-000c297bd0e6

4.ESXI服务器的原IP地址?

image-20240429182236168

192.168.8.122

5.EXSI服务器中共创建了几个虚拟机?

image-20240429181611919

4

6.网站服务器绑定的IP地址为?

image-20240429183012566

192.168.8.89

*使用单用户模式破解root密码

https://blog.csdn.net/Gao068465/article/details/130982814

1.系统启动进入到如下界面后输入字母“e”;

image-20240429202319534

2.在Linux16这一段的最后(UTF-8)加上

init=/bin/sh

image-20240429202655289

3.按下Ctrl X,进入到如下界面

image-20240429202716592

4.输入命令

mount -o remount,rw /

image-20240429202903469

5.修改root密码

passwd root

image-20240429202935881

6.输入命令

touch /.autorelabel

7.输入命令退出单用户模式

exec /sbin/init

image-20240429203039027

8.出现如下界面,等待即可

image-20240429203052755

*密码绕过总结

单用户绕过密码

找到linux16开头的行,在这行的末尾添加init=/bin/bash
按下Ctrl + X启动系统
mount -o remount,rw /
passwd root  # 修改root用户的密码,如果需要
touch /.autorelabel  # 如果SELinux被启用,创建这个文件来重新计算文件的安全上下文
exec /sbin/init

7.网站服务器的登录密码为?

找到网站服务器对应的虚拟机,其对应的VMDK文件为www-flat.vmdk,导出vmdk或者ftk挂载ESXi的E01,使用hashcat等爆破软件破解源检材中的/etc/shadow文件即可。

hashcat -m 1800 shadow -a 3 ?l?l?l?l?l?l
hashcat -m 1800 shadow -a 0 commonPwd.txt

image-20240506091639795

image-20240506091715281

qqqqqq

8.网站服务器所使用的管理面板登陆入口地址对应的端口号为:

配置文件GATWAY错了。。。

image-20240430101607008

改了

image-20240430104655169

上述忽略........

image-20240430125034921

14131

9.网站服务器的web目录是?

打开宝塔,没有配置文件

history也被清空

image-20240430193537948

/webapp

*jar服务器搭建

先在MANIFEST.MF找入口

image-20240430174201866

发现主体架构

修改jar包

image-20240430184641614

Mysql配置:

把ip改了,把用户名密码改了

image-20240430185144053

Redis配置:

改为ip

image-20240430185020337

java -jar ruoyi-admin.jar

报错,修改

image-20240430185652426

[root@localhost webapp]# nohup: 把输出追加到"nohup.out"
[root@localhost webapp]# java -jar ruoyi-admin.jar
Application Version: 3.8.2
Spring Boot Version: 2.5.13
////////////////////////////////////////////////////////////////////
//                          _ooOoo_                               //
//                         o8888888o                              //
//                         88" . "88                              //
//                         (| ^_^ |)                              //
//                         O\  =  /O                              //
//                      ____/`---'\____                           //
//                    .'  \\|     |//  `.                         //
//                   /  \\|||  :  |||//  \                        //
//                  /  _||||| -:- |||||-  \                       //
//                  |   | \\\  -  /// |   |                       //
//                  | \_|  ''\---/''  |   |                       //
//                  \  .-\__  `-`  ___/-. /                       //
//                ___`. .'  /--.--\  `. . ___                     //
//              ."" '<  `.___\_<|>_/___.'  >'"".                  //
//            | | :  `- \`.;`\ _ /`;.`/ - ` : | |                 //
//            \  \ `-.   \_ __\ /__ _/   .-` /  /                 //
//      ========`-.____`-.___\_____/___.-`____.-'========         //
//                           `=---='                              //
//      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^        //
//             佛祖保佑       永不宕机      永无BUG               //
////////////////////////////////////////////////////////////////////
17:51:02.920 [background-preinit] INFO  o.h.v.i.util.Version - [<clinit>,21] - HV000001: Hibernate Validator 6.2.3.Final
17:51:22.927 [main] WARN  o.s.b.StartupInfoLogger - [appendOn,117] - InetAddress.getLocalHost().getHostName() took 20018 milliseconds to respond. Please verify your network configuration.
17:51:42.946 [main] INFO  c.r.RuoYiApplication - [logStarting,55] - Starting RuoYiApplication using Java 1.8.0_311 on localhost.localdomain with PID 25167 (/webapp/ruoyi-admin.jar started by root in /webapp)
17:51:42.952 [main] DEBUG c.r.RuoYiApplication - [logStarting,56] - Running with Spring Boot v2.5.13, Spring v5.3.19
17:51:42.953 [main] INFO  c.r.RuoYiApplication - [logStartupProfileInfo,681] - The following 1 profile is active: "druid"
17:51:45.518 [main] INFO  o.a.c.h.Http11NioProtocol - [log,173] - Initializing ProtocolHandler ["http-nio-8080"]
17:51:45.518 [main] INFO  o.a.c.c.StandardService - [log,173] - Starting service [Tomcat]
17:51:45.518 [main] INFO  o.a.c.c.StandardEngine - [log,173] - Starting Servlet engine: [Apache Tomcat/9.0.62]
17:51:45.694 [main] INFO  o.a.c.c.C.[.[.[/] - [log,173] - Initializing Spring embedded WebApplicationContext
17:51:46.288 [main] DEBUG c.r.f.s.f.JwtAuthenticationTokenFilter - [init,242] - Filter 'jwtAuthenticationTokenFilter' configured for use
17:51:48.297 [main] INFO  org.redisson.Version - [logVersion,41] - Redisson 3.8.2
17:52:08.586 [redisson-netty-4-4] INFO  o.r.c.p.MasterPubSubConnectionPool - [operationComplete,168] - 1 connections initialized for 127.0.0.1/127.0.0.1:6379
17:52:08.587 [redisson-netty-4-4] INFO  o.r.c.p.MasterConnectionPool - [operationComplete,168] - 32 connections initialized for 127.0.0.1/127.0.0.1:6379
17:52:08.958 [main] INFO  c.a.d.p.DruidDataSource - [init,998] - {dataSource-1} inited
17:52:08.963 [main] DEBUG c.r.s.m.S.selectConfigList - [debug,137] - ==>  Preparing: select config_id, config_name, config_key, config_value, config_type, create_by, create_time, update_by, update_time, remark from sys_config
17:52:09.097 [main] DEBUG c.r.s.m.S.selectConfigList - [debug,137] - ==> Parameters: 
17:52:09.132 [main] DEBUG c.r.s.m.S.selectConfigList - [debug,137] - <==      Total: 24
17:52:09.552 [main] DEBUG c.r.s.m.S.selectDictDataList - [debug,137] - ==>  Preparing: select dict_code, dict_sort, dict_label, dict_value, dict_type, css_class, list_class, is_default, status, create_by, create_time, remark from sys_dict_data WHERE status = ? order by dict_sort asc
17:52:09.558 [main] DEBUG c.r.s.m.S.selectDictDataList - [debug,137] - ==> Parameters: 0(String)
17:52:09.569 [main] DEBUG c.r.s.m.S.selectDictDataList - [debug,137] - <==      Total: 59
17:52:10.399 [main] INFO  o.q.i.StdSchedulerFactory - [instantiate,1220] - Using default implementation for ThreadExecutor
17:52:10.410 [main] INFO  o.q.c.SchedulerSignalerImpl - [<init>,61] - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
17:52:10.410 [main] INFO  o.q.c.QuartzScheduler - [<init>,229] - Quartz Scheduler v.2.3.2 created.
17:52:10.411 [main] INFO  o.q.s.RAMJobStore - [initialize,155] - RAMJobStore initialized.
17:52:10.411 [main] INFO  o.q.c.QuartzScheduler - [initialize,294] - Scheduler meta-data: Quartz Scheduler (v2.3.2) 'quartzScheduler' with instanceId 'NON_CLUSTERED'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  NOT STARTED.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
  Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.

17:52:10.411 [main] INFO  o.q.i.StdSchedulerFactory - [instantiate,1374] - Quartz scheduler 'quartzScheduler' initialized from an externally provided properties instance.
17:52:10.411 [main] INFO  o.q.i.StdSchedulerFactory - [instantiate,1378] - Quartz scheduler version: 2.3.2
17:52:10.411 [main] INFO  o.q.c.QuartzScheduler - [setJobFactory,2293] - JobFactory set to: org.springframework.scheduling.quartz.SpringBeanJobFactory@552518c3
17:52:10.423 [main] DEBUG c.r.q.m.S.selectJobAll - [debug,137] - ==>  Preparing: select job_id, job_name, job_group, invoke_target, cron_expression, misfire_policy, concurrent, status, create_by, create_time, remark from sys_job
17:52:10.423 [main] DEBUG c.r.q.m.S.selectJobAll - [debug,137] - ==> Parameters: 
17:52:10.428 [main] DEBUG c.r.q.m.S.selectJobAll - [debug,137] - <==      Total: 2
17:52:10.436 [main] WARN  o.s.b.w.s.c.AnnotationConfigServletWebServerApplicationContext - [refresh,591] - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'sysJobController': Unsatisfied dependency expressed through field 'jobService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sysJobServiceImpl': Invocation of init method failed; nested exception is org.quartz.SchedulerException: Based on configured schedule, the given trigger 'DEFAULT.TASK_CLASS_NAME105' will never fire.
17:52:10.436 [main] INFO  o.q.c.QuartzScheduler - [shutdown,666] - Scheduler quartzScheduler_$_NON_CLUSTERED shutting down.
17:52:10.436 [main] INFO  o.q.c.QuartzScheduler - [standby,585] - Scheduler quartzScheduler_$_NON_CLUSTERED paused.
17:52:10.436 [main] INFO  o.q.c.QuartzScheduler - [shutdown,740] - Scheduler quartzScheduler_$_NON_CLUSTERED shutdown complete.
17:52:10.436 [main] INFO  sys-user - [shutdownAsyncManager,31] - ====关闭后台任务任务线程池====
17:52:10.437 [main] WARN  o.s.c.a.CommonAnnotationBeanPostProcessor - [postProcessBeforeDestruction,185] - Destroy method on bean with name 'shutdownManager' threw an exception: java.lang.ExceptionInInitializerError
17:52:10.473 [main] INFO  c.a.d.p.DruidDataSource - [close,2071] - {dataSource-1} closing ...
17:52:10.478 [main] INFO  c.a.d.p.DruidDataSource - [close,2144] - {dataSource-1} closed
17:52:10.596 [main] INFO  o.a.c.c.StandardService - [log,173] - Stopping service [Tomcat]
17:52:10.616 [main] ERROR o.s.b.SpringApplication - [reportFailure,865] - Application run failed
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'sysJobController': Unsatisfied dependency expressed through field 'jobService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sysJobServiceImpl': Invocation of init method failed; nested exception is org.quartz.SchedulerException: Based on configured schedule, the given trigger 'DEFAULT.TASK_CLASS_NAME105' will never fire.
        at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.resolveFieldValue(AutowiredAnnotationBeanPostProcessor.java:659)
        at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:639)
        at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:119)
        at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessProperties(AutowiredAnnotationBeanPostProcessor.java:399)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1431)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:619)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542)
        at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)
        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:953)
        at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583)
        at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145)
        at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775)
        at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:448)
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:339)
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:1365)
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:1354)
        at com.ruoyi.RuoYiApplication.main(RuoYiApplication.java:18)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
        at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
        at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
        at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sysJobServiceImpl': Invocation of init method failed; nested exception is org.quartz.SchedulerException: Based on configured schedule, the given trigger 'DEFAULT.TASK_CLASS_NAME105' will never fire.
        at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:160)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:440)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1796)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:620)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542)
        at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)
        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
        at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:276)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1389)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1309)
        at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.resolveFieldValue(AutowiredAnnotationBeanPostProcessor.java:656)
        ... 28 common frames omitted
Caused by: org.quartz.SchedulerException: Based on configured schedule, the given trigger 'DEFAULT.TASK_CLASS_NAME105' will never fire.
        at org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:851)
        at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:249)
        at com.ruoyi.quartz.util.ScheduleUtils.createScheduleJob(ScheduleUtils.java:86)
        at com.ruoyi.quartz.service.impl.SysJobServiceImpl.init(SysJobServiceImpl.java:44)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:389)
        at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:333)
        at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:157)
        ... 40 common frames omitted

这个错误信息显示了在创建名为 sysJobController 的 bean 时出现了依赖不满足的问题,具体是 jobService 这个字段

image-20240430184737057

搭建成功

image-20240430191900905

10.网站配置中Redis的连接超时时间为多少秒

image-20240430124957459

10

11.网站普通用户密码中使用的盐值

image-20240430125231772

image-20240430125258958

普通用户登录逻辑:com.ruoyi.app.service.impl.UserInfoServiceImpl.login

image-20240430130048943

!@#qaaxcfvghhjllj788+)_)((

12.网站管理员用户密码的加密算法是什么

A.des
B.rsa
C.md5
D.bcrypt

(1)Des为对称加密,一般不用做密码加密,解密需要密钥;

(2)Rsa为非对称加密,一般也不用做密码而是密钥,结果一般为hex或者base64格式;

(3)Md5常见密码加密策略,这个大家应该都熟,结果为16/32位hex;

(4)Bcrypt常见密码加密策略,linux的shadow文件经典加密算法。特征为有多个$符号隔开。

$2a$10$是bcrypt哈希算法生成的密码哈希值

image-20240430192301547

D

13.网站超级管理员用户账号创建的时间是?

A.2022-05-09 12:44:41
B.2022-05-09 13:44:41
C.2022-05-09 14:44:41
D.2022-05-09 15:44:41

image-20240430192433580

C

14.重构进入网站之后,用户管理下的用户列表页面默认有多少页面数据

image-20240430192735019

$2a$10$CtRvvfuulgkli8lgcFSuOeQZ3unTTPpg72Nk.BSJ3SeVraPRWyIdm

image-20240430192816222

image-20240430192957754

image-20240430193220856

877

15.网站的系统接口文档版本号为

image-20240430193714585

3.8.2

16.网站获取订单列表的接口

image-20240430193735439

/api/shopOrder

17.受害人卢某的用户ID

image-20240430194002811

搜索账号lu123456

image-20240430200207327

10044888

18.受害人卢其中共充值了多少钱

image-20240430200229803

465222

19.网站设置的单次抽奖价格为多少元

image-20240430200302334

10

20.网站显示的总余额是

image-20240430200422584

7354468.56

21.网站数据库的root密码

image-20240429205242875

my-secret-pw

22.数据库服务器的操作系统版本是

image-20240429205711842

7.9.2009

23.数据库服务器的DockerServer版本是

docker version
image-20240429205453039

1.13.1

24.数据库服务器中数据库容器的完整ID是

image-20240506092455505

image-20240430132257951

9bf1cecec3957a5cd23c24c0915b7d3dd9be5238322ca5646e3d9e708371b765

25.数据库服务器中数据库容器使用的镜像ID

image-20240506092504691

image-20240430132251112

66c0e7ca4921e941cbdbda9e92242f07fe37c2bcbbaac4af701b4934dfc41d8a

26.数据库服务器中数据库容器创建的北京时间

A.2024/3/13 12:15:23
B.2024/3/13 20:15:23
C.2024/3/14 00:15:23
D.2024/3/13 08:15:23

docker inspect 9b
image-20240430132514025

北京时间再加8小时

B

27.数据库服务器中数据库容器的ip是

image-20240430132436158

172.17.0.2

28.分析数据库数据,在该平台邀请用户输入和最多用户的登录IP是

app_group_apply群聊邀请表
app_user_info用户信息表

image-20240430200759792

status=1为邀请成功

SELECT inviter_id,COUNT(*) as count
FROM app_group_apply
WHERE status=1
GROUP BY inviter_id
ORDER BY count DESC;

image-20240430204700588

用户id为53576061

image-20240430204804237

223.104.51.34

29.分析数据库数据,在该平台抢得最多红包金额的用户的登录IP是

app_group_redpacket member
群红包表
ap_user info
用户信息表

SELECT user_id,SUM(money) FROM `app_group_redpacket_member` GROUP BY user_id ORDER BY SUM(money) desc

image-20240430205008892

user_id为90671142

image-20240430205036672

116.62.104.130

30.数据库中记录的提现成功的金额总记是多少(不考虑手续费)

app_user_withdraw提现表

status=3为提现成功

SELECT sum(amount) FROM `app_user_withdraw` where `status`=3

image-20240430205747552

35821148.48

31.rocketchat服务器中,有几个真实用户?

image-20240430210206487

image-20240430213100001

image-20240430213234221

或者

image-20240506092623667

3

32.RocketChat服务器中,聊天服务的端口号是?

3000

33.Rocketchat服务器中,聊天服务管理员的邮箱是?

admin@admin

34.RocketChat服务器中,聊天服务使用的数据库的版本号是?

image-20240430213434159

5.0.24

35.Rocketchat服务器中,最大的文件上传大小是?(以字节为单位)

image-20240430213612531

104857600

36.Rocketchat服务器中,管理员账号的创建时间为?

A.2024/3/14 8:18:54
B.2024/3/14 8:19:54
C.2024/3/14 8:17:54
D.2024/3/14 8:15:54

image-20240430215310824

ssh连接服务器

image-20240430220012279image-20240430220025209

image-20240430220138358

B

37.Rocketchat服务器中,技术人员提供的涉诈骗网站地址是?

image-20240430220213885

http://172.16.80.47

38.综合分析服务器,该团伙的利润分配方案中,老李的利润活动是多少

image-20240430215725548

35%

39.综合分析服务器,该团队“杀猪盘”收网的可能时间段为

A.2024/3/15 15:00:00-16:00:00
B.2024/3/15 16:00:00-17:00:00
C.2024/3/15 17:00:00-18:00:00
D.2024/3/15 18:00:00-19:00:00

image-20240430215817076

B

40.请综合分析,警方未抓获的重要嫌疑人,其使用聊天平台时注册邮箱号为?

image-20240430214436255

lao@su.com

41.分析openwrt镜像,该系统的主机名为

image-20240429184455244

iStoreOS

42.分析openwrt镜像,该系统的内核版本为

image-20240506092733054

5.10.201

43.分析openwrt镜像,该静态ip地址为

cat /etc/config/network

image-20240429200126130

192.168.8.5

44.分析openwrt镜像,所用的网卡的名称为

image-20240430220854422

eth0

45.分析openwrt镜像,该系统中装的docker的版本号为

docker version

image-20240430220925609

20.10.22

46.分析openwrt镜像,nastools的配置文件路径为

image-20240430221032479

/root/Configs/NasTools

47.分析openwrt镜像,使用的vpn代理软件为

image-20240430221107994

不是Core

注意看左边,PassWall2

passwall2

48.分析openwrt镜像,vpn实际有多少个可用节点

image-20240430221150947

image-20240430221241593

54-1=53

53

49.分析openwrt转发,节点socks的监听端口是多少

image-20240430221732846

1070

50.分析openwrt镜像,vpn的订阅链接是

image-20240430221302629

https://pqjc.site/api/v1/client/subscribe?token=243d7bf31ca985f8d496ce078333196a

窗口镜像

1.分析技术员赵某的windows镜像,并计算赵某计算机的原始镜像的SHA1值?

FFD2777C0B966D5FC07F2BAED1DA5782F8DE5AD6

2.分析技术员赵某的windows镜像,疑似VeraCrypt加密容器的文件的SHA1值?

B25E2804B586394778C800D410ED7BCDC05A19C8

3.根据赵某供述,他将常用的密码放置在一个文档内,分析技术员赵某的windows镜像,找到技术员赵某的密码字典,并计算该文件的SHA1值?

image-20240430083140156

image-20240430083320339

e6eb3d28c53e903a71880961abb553ef09089007

4.根据赵某供述,他将加密容器的密码隐写在一张图片内,隐写在图片中的容器密码是?

用记事本打开

image-20240430083417590

qwerasdfzxcv

5.分析技术员赵某的windows镜像,bitlocker的恢复密钥是什么

image-20240429185308095image-20240429185342628

推测在vc容器里

image-20240430083524178

image-20240430083607189

404052-011088-453090-291500-377751-349536-330429-257235

6.分析技术员赵某的windows镜像,bitlocker分区的起始扇区数是

image-20240430224040178

146794496

7.分析技术员赵某的windows镜像,默认的浏览器是

image-20240430083855226

Chrome

8.分析技术员赵某的windows,中部聊天服务器的密码为

bitlocker里面的

image-20240430085750152

Zhao

9.分析技术员赵某的windows镜像,怀疑人计算机疑似使用AI技术生成的赌博宣传图片,该图片中,宣传的赌博网站地址为?

进入bitlocker加密的盘

image-20240430085216282

image-20240430085246432

www.585975.com

10.分析技术员赵某的windows镜像,赵某使用的AI换脸工具名称为?

image-20240430084856711

roop

11.分析技术员赵某的windows镜像,使用AI换脸功能生成了一张图片,该图片的名称为

image-20240430085306557

db.jpg

12.分析技术员赵某的windows镜像,ai换脸生成图片的参数中--similar-face-distance值

image-20240430085617471

0.85

13.分析技术员赵某的windows镜像,嫌疑人使用AI换脸功能所使用的原始图片名称为

image-20240430085333730

2.png

14.分析技术员赵某的windows镜像,赵某与李某沟通中提到的“二维码”解密所用的网站url地址为?

image-20240430085354682

http://hi.pcmoe.net/buddha.html

15.分析技术员赵某的windows镜像,赵某架设聊天服务器的原始IP地址为?

分析可得

192.168.8.17

16.分析技术员赵某的windows镜像,据赵某交代,其在窝点中直接操作服务器进行部署,环境搭建好之后,使用个人计算机登录聊天室进行沟通,请分析赵某第一次访问聊天室的时间为?

A.2024-03-14 20:30:08
B.2024-03-14 20:31:08
C.2024-03-14 20:32:08
D.2024-03-14 20:33:08

image-20240430090159572

C

17.分析技术员赵某的windows镜像,openwrt的后台管理密码是

image-20240430084002101

hl@7001

18.分析技术员赵某的windows镜像,嫌疑人可能使用什么云来进行文件存储?

image-20240430090225193

易有云

19.分析技术员赵某的windows镜像,工资表密码是多少

爆破

image-20240430090610314

image-20240430090647225

image-20240430090704693

aa123456

20.分析技术员赵某的windows镜像,张伟的工资是多少

image-20240430090751297

28300

posted @ 2026-06-11 14:27  Cava1i  阅读(11)  评论(0)    收藏  举报